0 Comments
Drupal.org is the home of the Drupal community, and in its 20 year history Drupal.org has managed to coordinate and centralize the efforts of our contributors. As we look to recruit the next generation of contributors who will become project leaders in the next decade, we want to reduce the barriers to joining the community, and extend the reach of a user's Drupal identity. As such, the Drupal Association is undertaking a new project to both allow account creation and authentication to Drupal.org using common existing accounts that new contributors may already have, and allow federation of the Drupal.org identity, so third party community services like DrupalCamp sites or chat services can allow users to log in with their Drupal identity. Successful completion of this project will allow new contributors to Drupal to join the community in a single click(or as close as possible with Terms acceptance, etc), and will allow existing Drupal.org users to join community-built services with their existing Drupal.org identity. ScopeProject scope should include Discovery, Project Management, Development, Security Review, and Quality Assurance for the following key features:
Technical constraints and additional requirementsThe chosen solution must meet the following additional technical constraints and requirements:
Vendor requirementsThe Drupal Association will consider contracts from both individual developers and agencies. An individual must:
An agency must:
Other Considerations:Please indicate if you’re willing to accept in-kind benefits if your bid comes in higher than our allocated budget. The cash portion of the budget should not exceed $28,000 USD. The point person for this project at the Drupal Association is generally available between 4:00 PM - 11:00 PM UTC. We welcome global responses but we’d prefer meeting times to be within our standard business hours. We will make every effort to accommodate times outside of standard Pacific Time business hours. TimelineWe would like the authentication and identity solution to be implemented no later than October 1st, 2021. Individuals or Agencies who intend to participate should provide their bids and samples of portfolio work to the Drupal Association via email ([email protected]) no later than Friday, May 14th at 5pm U.S. Pacific. Respondents will be notified of the decision no later than June 15th. Originally from Drupal.org aggregator https://ift.tt/3vyLLWc Drupal.org is the home of the Drupal community, and in its 20 year history Drupal.org has managed to coordinate and centralize the efforts of our contributors. As we look to recruit the next generation of contributors who will become project leaders in the next decade, we want to reduce the barriers to joining the community, and extend the reach of a user's Drupal identity. As such, the Drupal Association is undertaking a new project to both allow account creation and authentication to Drupal.org using common existing accounts that new contributors may already have, and allow federation of the Drupal.org identity, so third party community services like DrupalCamp sites or chat services can allow users to log in with their Drupal identity. Successful completion of this project will allow new contributors to Drupal to join the community in a single click(or as close as possible with Terms acceptance, etc), and will allow existing Drupal.org users to join community-built services with their existing Drupal.org identity. ScopeProject scope should include Discovery, Project Management, Development, Security Review, and Quality Assurance for the following key features:
Technical constraints and additional requirementsThe chosen solution must meet the following additional technical constraints and requirements:
Vendor requirementsThe Drupal Association will consider contracts from both individual developers and agencies. An individual must:
An agency must:
Other Considerations:Please indicate if you’re willing to accept in-kind benefits if your bid comes in higher than our allocated budget. The cash portion of the budget should not exceed $28,000 USD. The point person for this project at the Drupal Association is generally available between 4:00 PM - 11:00 PM UTC. We welcome global responses but we’d prefer meeting times to be within our standard business hours. We will make every effort to accommodate times outside of standard Pacific Time business hours. TimelineWe would like the authentication and identity solution to be implemented no later than October 1st, 2021. Individuals or Agencies who intend to participate should provide their bids and samples of portfolio work to the Drupal Association via email ([email protected]) no later than Friday, May 14th at 5pm U.S. Pacific. Respondents will be notified of the decision no later than June 15th. Originally from Drupal.org aggregator https://ift.tt/3vyLLWc There are more than 1 million Drupal sites actively in use across the globe. At least one in 40 websites that a typical internet user visits is likely to be built on Drupal - however, the Drupal project leads and the Drupal Association do not necessarily have a direct line of communication to each of these Drupal site owners. While the Association can reach Drupal users and site owners who visit Drupal.org, attend DrupalCon, or follow one of our social channels, there are many more users who do not engage with the Drupal community outside of their own Drupal instance control panel. This initiative seeks to change that by adding a channel for important project and association messaging directly in Drupal Core's admin interface. ScopeThe feature proposal has already completed the core idea queue process, and the initial prototype of the Project Messaging in Core feature has already been built as a contributed module. This existing work currently needs to be transferred into a true core feature request issue with added test coverage and any additional changes requested by the core team. The work then needs to be backported to Drupal 7, and possibly to Drupal 8 after discussion with core maintainers.
Technical constraints and additional requirementsThe chosen solution must meet the following additional technical constraints and requirements:
Vendor requirementsThe Drupal Association will consider contracts from both individual developers and agencies. An individual must:
An agency must:
Other Considerations:Please indicate if you’re willing to accept in-kind benefits if your bid comes in higher than our allocated budget. The cash portion of the budget should not exceed $30,000 USD. The point person for this project at the Drupal Association is generally available between 4:00 PM - 11:00 PM UTC. We welcome global responses but we’d prefer meeting times to be within our standard business hours. We will make every effort to accommodate times outside of standard Pacific Time business hours. TimelineThe project messaging feature has a hard deadline of October 1st, 2021 in order to be included in the last release of Drupal 9, and for a backported release to Drupal 7. Preference will be given to proposals that complete the work on a much shorter timeline in order to allow plenty of time for the core acceptance process. Individuals or Agencies who intend to participate should provide their bids and samples of portfolio work to the Drupal Association via email ([email protected]) no later than Friday, May 14th at 5pm U.S. Pacific. Respondents will be notified of the decision no later than June 15th. Originally from Drupal.org aggregator https://ift.tt/2R93LHI Originally from Drupal.org aggregator https://ift.tt/3ucpgWU
This DrupalFest series of posts is about to end and I thought that a fitting end would be to talk about the future of Drupal. I have already written a bit about this in my previous post: what I want to see in Drupal 10. However, this post is more aspirational and even dream-like. Some of these may sound really far-fetched and it may not even be clear how to get there. For the purposes of this post, that's fine. I will not only worry about the how; just the what.
Originally from Drupal.org aggregator https://ift.tt/3e5Ff3f
Hello there! In this new post I want to focus on a very interesting topic of Drupal, which pertains to its extension capabilities through its Plugins system. It is not a very extensive topic, but it is also true that there is not much documentation about it. This is a very common case when you’re building some kinds of Drupal Blocks in order to render specific data and you need that its visualization and its behaviour responds to special conditions. Picture from Unsplash, user Benjamin Child, @@bchild311 Table of Contents 1- Introduction Originally from Drupal.org aggregator https://ift.tt/2QFsNOE Currently LocalGov Drupal relies on Bootstrap for its grid system. I think we can achieve a really nice grid system with about 30 lines of CSS. Let's see! Originally from Drupal.org aggregator https://ift.tt/3eGQsGv
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
April 2023
Categories |