| chrisfromredfin |
DOH! It looks like @timplunkett (he/him) DID tag an alpha already at the end of yesterday, which means that the SBS did sign off on usability issues! |
| chrisfromredfin |
:raised_hands: :raised_hands: :raised_hands: |
| chrisfromredfin |
I will send an update/email to Dries. Does @Gábor Hojtsy (he/him) know of the best avenue to make an announcement somewhere to the community? |
| chrisfromredfin |
I have asked to include it in the #talkingdrupal newsletter. |
| timplunkett (he/him) |
oh, I thought I announced it to the channel! whoops :slightly_smiling_face: |
| timplunkett (he/him) |
but now can we have a discussion in a new thread about beta/stable? |
| chrisfromredfin |
thread 2! |
| Gábor Hojtsy (he/him) |
It should all be within your realm of definition to tag an alpha/beta, no need to ask for permission from anyone IMHO. Core will be a different question :) |
| chrisfromredfin |
Right, my intention was just to have that discussion internally here to see what we thought. |
| chrisfromredfin |
But was hoping you would have insight into how we could communicate this out to the community at large, @Gábor Hojtsy (he/him) - Drupal.org newsletter, or something? |
| timplunkett (he/him) |
I'm starting a new thread just about MVP/1.0 since that one is discussing 1.1/2.0 stuff |
| Gábor Hojtsy (he/him) |
Is this thread now for how to promote it? |
| chrisfromredfin |
It is now that I realized the alpha was already tagged, so yes :slightly_smiling_face: |
| Gábor Hojtsy (he/him) |
SURPRISE! You’ve been on the /download page for a week now :stuck_out_tongue: https://www.drupal.org/download |
| Gábor Hojtsy (he/him) |
Links to https://www.drupal.org/about/preview-features |
| Gábor Hojtsy (he/him) |
Happy to update the text/screenshot/button there now that you have an alpha :slightly_smiling_face: |
| chrisfromredfin |
Aww darn - but we're broken on simplytest.me right now! |
| chrisfromredfin |
:slightly_smiling_face: |
| Gábor Hojtsy (he/him) |
I did not make big noise about this until you have a tagged version which we can link to :smile: |
| Gábor Hojtsy (he/him) |
yeah it worked when I tried last week |
| chrisfromredfin |
pending this one -> #3285253: Error: Got a packet bigger than 'max_allowed_packet' bytes |
| Gábor Hojtsy (he/him) |
Ah that, I may have experienced that at one point yeah |
| timplunkett (he/him) |
so we have 1 MVP issue left, which is a straightforward a11y fix |
| timplunkett (he/him) |
@fjgarlin’s work is not currently tagged as MVP blocking |
| timplunkett (he/him) |
we added the disclaimer in https://www.drupal.org/i/3282732 to not hold things up, and to be able to ship with the fixture data |
| timplunkett (he/him) |
(here's the new thread @chrisfromredfin ) |
| fjgarlin |
[#3240319]Plugin is ready. D9 www.drupal.org migration + jsonapi is ready.Infra is not ready yet, so we don’t have an endpoint. I’m asking about this.I have control over 1 and 2, but not 3. |
| chrisfromredfin |
We've made a lot of hacks to do with the fixture as well, and if we're really going to have a 1.0 then we may consider making the fixture updater a first-class thing? |
| timplunkett (he/him) |
the end user experience should be identical when we merge that issue, correct? |
| timplunkett (he/him) |
@chrisfromredfin isn't that why we just finished https://www.drupal.org/i/3292562 ? |
| chrisfromredfin |
Only exception would be the speed (making real-time API calls vs. querying a fixture on the local Drupal site) and having up-to-the-cache data. |
| fjgarlin |
re 3. there were some higher priorities to be addressed by the DA before tacking this. we’re close, but not quite there yet. |
| chrisfromredfin |
Yes but in that issue @timplunkett (he/him) @narendraR had some feedback that we largely ignored because "this is throwaway code" |
| timplunkett (he/him) |
just dependency injection |
| fjgarlin |
correct. end user experience remains identical, with the exception of the speed as Chris pointed out |
| timplunkett (he/him) |
removing \Drupal:: service calls |
| timplunkett (he/him) |
so the speed is BETTER now and will only degrade :wink: if it was the other way, I'd be happier to wait for it |
| chrisfromredfin |
Could we compromise on a time limit? Like if we think we'll have Fran's #3 (above) in... 6 weeks, we'll let it block. But if it's longer than that, we won't? |
| chrisfromredfin |
it's odd to me to have a fully functional 1.0 that we're giving to users but then saying "but if you want updated data be sure to update your module" |
| timplunkett (he/him) |
that's 6 more weeks of people not installing it because it's alpha, meaning 6 weeks of less user feedback |
| timplunkett (he/him) |
but what is actually changing? |
| timplunkett (he/him) |
the number of installs, but not really RELATIVE to each other |
| timplunkett (he/him) |
it's not like ctools is going anywhere |
| fjgarlin |
I think 6 weeks sound quite reasonable, but can’t really say it 100%.we do have a server already on a very similarly structured project (api.drupa.org D9), so the set up of the new one will be similar, with a few caveats (solr, migrations…) |
| chrisfromredfin |
All the work @leslieg’s team is doing to update logos, categories, descriptions, for one. |
| bnjmnm |
It wouldn't be THAT hard to add a cron that gets the data current every x hours |
| chrisfromredfin |
^ That's another thought. Some kind of built-in where a user could click "update data from Drupal.org" and through batch API it could update? That's a lot of hits to d.o from users, though. Especially against the old api. |
| timplunkett (he/him) |
no that's a nonstarter |
| bnjmnm |
Ah ok |
| chrisfromredfin |
How come? |
| timplunkett (he/him) |
we can't ship anything runtime hitting the old API |
| chrisfromredfin |
like per drumm? |
| timplunkett (he/him) |
yes |
| chrisfromredfin |
k |
| chrisfromredfin |
Again, we're talking about this blocking RC - does advancing to beta still on the fixture provide any kind of alleviation to you tim? |
| timplunkett (he/him) |
beta and rc are both the same to me. I want the 1.0 |
| fjgarlin |
that’s 6 more weeks of people not installing it because it’s alpha, meaning 6 weeks of less user feedbackthat’s why perhaps this issue should just target rc and not beta? |
| chrisfromredfin |
Or you think we won't see trials/usage/feedback until it's a real 1.0 |
| timplunkett (he/him) |
^ |
| timplunkett (he/him) |
we're not going to get real people to use this until it's stable. that's where the bug reports and feature requests will come from |
| chrisfromredfin |
I can't say I totally disagree with that. |
| timplunkett (he/him) |
and since the method of the data getting to the user is transparent to them, that's why I'm not concerned about waiting. the UI is what we need feedback on |
| chrisfromredfin |
would you be comfortable doing a point release every two weeks? |
| chrisfromredfin |
with updated fixture data (plus whatever else we ship?) |
| timplunkett (he/him) |
1.0.1 with bugfixes and data updates, 1.1.0 with new things, etc |
| chrisfromredfin |
Because we DO intend to make changes to the most important data (top 100 modules people will see with default filters) rapidly over the next month or two |
| chrisfromredfin |
yeah, like x.x.1 with data updated, .x.x.2 more data and bugs, etc |
| timplunkett (he/him) |
i'd be thrilled to get those updates out to people rapidly |
| chrisfromredfin |
ok, I'd be willing to take that on (just running the generated data script every other week) |
| fjgarlin |
I’m happy to show you guys at any point how the api works in my machine or go through the code of the plugin or even the D9 site. switching to the api plugin brings literally no changes, other than actual content from the jsonapi instead of the mock. |
| chrisfromredfin |
and pushing that in |
| leslieg |
From my standpoint, the issue with a Beta release at this point is that the data on drupal.org presented in project browser on grid and list views is not that useful to our target audiences. We need time to get that updated |
| timplunkett (he/him) |
but to that point |
| timplunkett (he/him) |
let's say that the endpoint was done already and we were pulling live data |
| chrisfromredfin |
^ oh? Like what, the number of installs etc leslie, is not useful data? Like you haven't gotten good feedback and what's on the card? |
| timplunkett (he/him) |
would we hold up a 1.0 until you made more headway on the d.o project updates? |
| leslieg |
no, I was thinking the categories and descriptions - the Top 100 we are working on |
| timplunkett (he/him) |
because I think the feedback on the presentation of the data is different than what the data says |
| chrisfromredfin |
I can be convinced to ship 1.0 with the disclaimer message then, and with data updates every two weeks. I may argue to change the disclaimer message to include "Please keep this module up to date to get the most recent available data" or something. |
| timplunkett (he/him) |
and if the category list gets smaller over time, that's great |
| chrisfromredfin |
And no, I wouldn't hold up a 1.0 on the Drupal data anyway. |
| chrisfromredfin |
That was always meant to be a rolling change. |
| leslieg |
agree - just don’t want folks to get initial impression that the project browser isn’t that useful based on what it returns |
| chrisfromredfin |
God you're persuasive, Tim. |
| chrisfromredfin |
I DO want to comb through the currently-filed issues and (potentially) tag some stuff MVP |
| chrisfromredfin |
I have not had a long enough period of time to just browse current issues. |
| chrisfromredfin |
I may try and do that this afternoon. |
| leslieg |
I will take a spin through as well for any UX related issues |
| timplunkett (he/him) |
Any updates? Today is the end of the quarter and it'd be good to have a sense of timeline for the next milestone |
fjgarlin, Webbeh, hestenet, chrisfromredfin, tim.plunkett, Gábor Hojtsy, leslieg, bnjmnm
Comments
Comment #9
leslieg commentedComment #10
leslieg commented