Hello one and all, to our weekly Project Browser meeting. We have a couple of things to discuss today, and will open it up if anyone else has questions / threads they'd like to add. NOTE: please introduce yourself in this thread, and IMPORTANT: If your drupal.org username is not the same as your Slack username, please let us know your d.o username when you introduce yourself. We need the d.o username to give credit for input! Thanks :slightly_smiling_face:

tim Hello Tim   hoping that we get modules more search-ablelets4
Rajab Natshah Hi, This is Rajab Natshah, a bit late today, catching up :slightly_smiling_face:
shaal Hi, Ofer Shaal, very late, catching up
mradcliffe Hi, Matthew here. Catching up.
jjcs227 Hello!, jj here, jjcs227 d.o username catching up with the meeting
el7cosmos Hi

1️⃣ Any additional thoughts on what might happen at DrupalCon? Leslie has been signing me up for stuff I don't fully understand yet, so maybe @leslieg can brief us on how we will be represented in Portland, and if there's any other thoughts, I'd love to hear them. I intend to spend much of my time in the coder lounge actually working on PB itself, but certainly wouldn't mind company! :slightly_smiling_face:

leslieg Current plans are:
leslieg 1. to have @chrisfromredfin be at a table in the General Contribution area to work with folks on the more technical issues discussed during our Wednesday PB meetings
leslieg 2. to have @leslieg at a table in the Mentored Contribution room to work on items that the PB Site Builder Subcommittee is working on. We will have novice issues for several of the Top 100 Modules to have folks work together to come up with easy to understand 1-2 sentence short Project Descriptions, logos if any design resources are available and to discuss appropriate categories for the module.
leslieg 3. Leslie will be leading a BOF to discuss how we might recommend updating the Project pages on Drupal.org to make things more consistent. We will let you know what time the BOF is scheduled for
leslieg 4. We hope to sign up for another BOF once we are onsite to discuss Categories and how we might recommend updating those across projects.
tim I am hoping, planning on being there. I don't know what my schedule is yet, but would at least say hi minimum, to spend time working on big project.
chrisfromredfin selected.gif
tim I am interested in technical and deep into Categories so would spend time both places probably.
leslieg @Gábor Hojtsy (he/him) Is there an Initiative Keynote this year? Let us know where Initiative Leads can help at DrupalCon
Gábor Hojtsy (he/him) @leslieg hm, DrupalCon Portland, I was not asked to organize an initiative leads keynote, so (a) some things will be represented in the Driesnote, I can make connections if that is helpful :slightly_smiling_face: (b) I think a general BoF about the initiative would be nice, either one of those specialised ones to be converted to a general one, or one more general one to inform people / demo / get feedback
Gábor Hojtsy (he/him) Otherwise I think these are great, for an initiative I think the golden trio is (a) letting people know (Driesnote and/or dedicated session) (b) involving them in discussions (general BoF and specific BoFs) and (c) involving them in doing things (the general and mentored contribution). That’s really all that you can do at DrupalCon and if you do these well, its going to be fantastic :slightly_smiling_face:
leslieg Thanks @Gábor Hojtsy (he/him) A general BOF about the initiative is a good idea. We’ll do that
Gábor Hojtsy (he/him) The there layers in the golden trio are let's say (just making it up here) information :arrow_forward: involvement :arrow_forward: co-creation, so they engage the person deeper and deeper. Contribution being in the end helps do the other things in order as well.
mradcliffe For mentored contribution, we need to triage specific tasks to move the initiative forward from promotion (distinct needs for this), contrib module description/logo help (4 contrib modules should be fine), and also coding work (2-4 issues would be fine picked from any other issues on the project browser issue queue).
chrisfromredfin My biggest thought right now is that there's "big work" in the queue, not a lot of quick-wins, and that's a bit of the roadblock. BUT, about a week or two before I do intend to tee up issues in the queue for just that reason. I think even you/me/AmyJune were theoretically going to sync up about that @mradcliffe
mradcliffe Yes, back at Drupal Europe, the out-of-the-box initiative did some prep about a week before the conference and then an afternoon before the contrib day. 2021 virtual, I think it was about the same for initiatives doing prep work amongst all the other drupalcon work that initiative leads and contributors needed to get done to present at DrupalCon (big shout out to initiative leads and contributors for all the work you for that)
Gábor Hojtsy (he/him) @chrisfromredfin hopefully project browser will be further in 2 months time so the issues will be different, that said there is always a category of work where you need feedback from user testing let's say, someone can develop a script that a mentored contributor can walk through with two other mentored contributors let's say

2 IMPORTANT ANNOUNCEMENT: No PB meeting next week. I'm taking a much-needed vacation. I would encourage people to use the time they would've spent in the meeting to comb through the issue queue and/or work on stuff!! <.h2>

3️⃣ Within a week or two, we'll have GitLab CI pipelines enabled for this project!! We can/should move our testing to there.

chrisfromredfin I know a good amount about GitLab CI - BUT, I don't know much about the testing we're doing thus far. Is it mostly PHP side? Anyone have any insights?
tim I don't have insights on testing. We were talking about doing it in nightwatch.  Is that what is being done?And Chris can you share more details the pipeline?
chrisfromredfin Basic overview / documentation is here. https://docs.gitlab.com/ee/ci/pipelines/
chrisfromredfin Basically, we could put a .gitlab-ci.yml in our repo and it would run our tests in there, rather than in the existing custom "DrupalCI" that runs it now. I would need any kind of primer on getting started with testing, or some hand-holding.
tim And we have got the runners figured out?
chrisfromredfin As far as I know, yes - git.drupalcode.org is providing runners to us afaik. we would just need to set up the gitlab-ci.yml
Rajab Natshah WOW .. nice . good to knowLearning how to switch for sure. :eyes:
chrisfromredfin What I don't know is like what commands kick off the tests, otherwise I'd be happy to take a stab after it becomes available to us.
fjgarlin I think that it’s yet not enabled for all projects. it might be soon, but the feature in in testing stages.you can find more info in #gitlab
chrisfromredfin Yes, Irina spoke with me yesterday and she put us in the queue to be enabled for alpha testing :slightly_smiling_face:
chrisfromredfin so we're gonna help shake the tree
Gábor Hojtsy (he/him) @chrisfromredfin you/we (community) should be getting guidance on those, I am sure the docs are ready somewhere, they are just not linked yet from #3261803: Using GitLab CI instead of Drupal CI :slightly_smiling_face:
mradcliffe Is there an issue in the project browser queue to work on the .gitlabci yaml config?
chrisfromredfin No, not yet, as it's not been enabled yet. I can file one when I hear back from Irina that it's ready; OR we (read: you :wink: ) could file one now and Postpone it?
mradcliffe I could. This would be a good opportunity for anyone who wants to be more familiar with creating issues to do so. :slightly_smiling_face:

Participants:

tim, Rajab Natshah, shaal, mradcliffe, jjcs227, el7cosmos, leslieg, chrisfromredfin, Gábor Hojtsy, fjgarlin

Comments

leslieg created an issue. See original summary.

leslieg credited Gábor Hojtsy.

leslieg credited Rajab Natshah.

leslieg credited chrisfromredfin.

leslieg credited el7cosmos.

leslieg credited fjgarlin.

leslieg credited jjcs227.

leslieg credited lets4.

leslieg credited mradcliffe.

leslieg credited shaal.

leslieg’s picture

leslieg commented
leslieg’s picture

leslieg commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.