The meeting kicked off roughly on time. It became immediately apparent that without someone from the Association there, we could not enable captioning. We were able to, after the meeting, sync up with someone from the Association (Tim L. / @hestenet) who provided credentials we can use to ensure host abilities are available in the future.
Ron Northcutt started by laying out an agenda. First up was an email from Dries announcing project leadership. Chris Wells (chrisfromredfin) and Ron Northcutt (rlnorthcutt) were assigned as co-initiative leads.
We reviewed the documents that Dries created which clarified goals, audience, and basic approach for the project. The first of these is the Project Brief document, which explains the problem, the audience who the solution should be implemented for, and the approach (as well as leadership structures). That document is here: https://docs.google.com/document/d/1qTimOmoEbqE-abQOu19D2ylvP36zGUvGTCxe...
These documents were created in a working session with Chris Wells, Ron Northcutt, Dries Buytaert, and Danielle Soares, with Dries providing much of the written words. Ron clarified that this document therefore primarily represents Dries's input, and not the entire group's. Though we should adhere to it, it is just that.
With the appointment of Initiative Leads, the discussion on leadership is not over. The general approach is to work out an MVP which uses Matt Grasmick's initial prototype (based off established UI in other projects), as well as coming up with a longer-term vision that iterates from that MVP. We are still looking for leaders in a number of roles that were brought forth from a working session of the Site Builder Sub-Committee.
![initiative leads, two site build leads, two dev leads, document lead, project manager, association liasion, contrib mentor/onboarding]()
In opening up the meeting to questions, Rajab agreed with the two phases and looks forward to contributing in the areas of coding, documentation, and testing.
Ron mentioned that Matt had made some quick decisions based on current limitations, and people should pull down the current MVP and test it out. Mihaela asked where that was, and we determined Matt was able to secure the "project_browser" namespace at https://drupal.org/project/project_browser - and that the 1.x-dev branch is his prototype. Ron is going to set up a demo site based on Matt's code so installation of a whole stack is not necessary to understand it. The code is also available on Github.
We are hoping to schedule a technical walk-through with Matt G. so he can demonstrate the internals of how the existing prototype is coded.
A concern was raised that there was no research going into the ideas of the prototype. Per Dries's thoughts, there is a huge amount of value that can be added to Drupal by using this with no research, and that is the MVP phase. The research will come as we iterate toward a core-committed version of the Project Browser that represents our second phase.
Mihaela had the question of - is it even possible to present an MVP without addressing the actual data/content of the project pages themselves? Do we need a "sub-initiative" to propose copy edits to project descriptions and screenshots/images using what we have now (perhaps a co-community-lead initiative between Project Browser Initiative and Marketing Initiative?).
Neil Drumm was able to speak up for the Association in response to Ron's comment that we cannot change the Drupal.org API in Phase I, which is actually not necessarily a limitation. We can build something on the current Drupal 7 site that is forward-looking to when Drupal.org (d.o) runs on Drupal 9. This means there IS an opportunity to think about good API design early on. So, there is certainly work to do in this area.
When Chris Wells asked about the timeline for the Drupal 9 upgrade, Neil re-iterated that we shouldn't let that be a blocker for this initiative.
Back to the topic of the actual content/data, Leslie Glynn voiced a concern that more than just the images and project descriptions need some curation, but also the "Category," which is self-selected by module maintainers. For example, AddToAny module (used for social sharing) shows up under the "Commerce" category, which may confuse users looking for add-ons to Drupal Commerce.
As to whether or not we approach these data corrections in Phase I or Phase II - well, that's what we need to decide. We still need to scope the MVP from the list of user stories. So, for next week (July 21), the plan is to review the prototype itself and capture general thoughts on strengths/weaknesses about it.
AmyJune asked about the deliverable / expectation for DrupalCon Europe. Ron thought the best goal was to be able to show some sort of progress on the initiative, be it simple screenshots or something for a presentation, but not necessarily anything super functional. That is, we are not under the wire to get something "done" by that time.
