I have a somewhat un-conventional idea to run past this group... The reality is that with all of the changes that have taken place in the social API space, there is very little code in github.com/apache/streams that has obvious end-user value today. The re-vitalization I've been pushing in 2024 (see threads linked below) is pretty in-line with the projects original goal, but not really served in any substance by the existing code base.
I think fair to say I am the sole remaining very strong proponent of this project on the PMC, and even I am now contributing toward the 'new' effort in a separate repository entirely, for a clean start. There are a few modules imported from apache-streams into apache-streams-activitypub, but not many. I don't have any immediate plans to keep working on the original code base other than version bumps and bug fixes. Potentially down the road if the basic activitypub server were fully implemented, then it would be interesting to start connecting up some of the data 'streams' into it, but that is uncertain and not any-time soon. Round-about way to say, what if we collectively accept some version of the above and retire 'Apache Streams' to the attic, and then take the new repo with the more specific and self-evidently important and valuable goal back to the incubator. Perhaps as 'Apache Pub'? On Sep 12, 2024 at 1:41 PM -0500, Brian Hodge <brianpho...@gmail.com>, wrote: > I have been drafting a more detailed response that I will send later this > evening. However, given Shane's message, I figure that signs of life are a > good thing. > > I am interested in keeping this project alive. At the absolute minimum, I > am following discussions like this one, and would be willing to step up if > the project needed urgent attention, such as a security fix. > > -Brian > > On Thu, Sep 12, 2024 at 11:31 AM Trevor Grant <trevor.d.gr...@gmail.com> > wrote: > > > Thanks Shane, > > > > fwiw, we've already had 3 PMCs (and others) respond* on this thread, so it > > looks like from that perspective anyway, we're good to go on that front. > > > > tg > > > > *Techincally one seeded (me) and two responded (Joey and Steve). > > > > On Thu, Sep 12, 2024 at 1:19 PM Shane Curcuru <a...@shanecurcuru.org> > > wrote: > > > > > > On 2024/09/10 18:34:21 Trevor Grant wrote: > > > > > > Y'all may or may not have seen, but someone called for us to be > > > > > > moved > > to > > > > > > the attic w/o a roll call earlier today. > > > > > > > > Thanks for raising the question here on the dev@ list, Trevor! > > > > > > > > For perspective: the ASF requires that PMCs have at least three active > > > > PMC members, such that (for example) someone would notice if a > > > > vulnerability were reported, and that the PMC could then make a release > > > > with any needed fixes. This is important, because end users expect that > > > > any "Apache GoodStuff" project would at least provide a basic level of > > > > security or other major fixes if needed. > > > > > > > > PMCs that can't show they have sufficient people able to reliably show > > > > up for urgent cases like that are sent to the Apache Attic - where the > > > > entirety of the project is turned read-only at it's existing URLs. > > > > While that shutters the active community here at the ASF, all the > > > > resources are available for anyone who wants to fork them. > > > > > > > > This thread is likely the last chance for this community to show there > > > > are sufficiently *active* volunteers who could step up to make future > > > > releases, otherwise, the board is likely to send the project to the > > > > Attic in mid-October. > > > > > > > > Thanks for all the past work, no matter which way this thread goes. > > > > > > > > -- > > > > - Shane > > > > Member > > > > The Apache Software Foundation > > > > > > > > > > I would like to propose one of three ways forward, and I'm curious > > > > > > who > > is > > > > > > even out there listening and would like to take part in the > > > > > > discussion. > > > > > > > > > > > > 1. Go to the attic... the right way - that is to say actually > > > > > > declare > > on > > > > > > the website we're going to be retiring the project and go through > > > > > > all > > of > > > > > > the motions of decommissioning/sunsetting software. > > > > > > > > > > > > 1a. Go to the attic ... the way proposed. Someone just slaps some > > > > > > 'abandoned' stickers on stuff, and everyone just walks away. > > > > > > > > > > > > 2. Revitalize the project - do people still use social media? Is > > > > > > this > > > > > > project in its current form still a viable concern. I ask in good > > faith- > > > > I > > > > > > occasionally will scroll insta or twitter, but I feel bad about > > > > > > myself > > > > when > > > > > > I do, and I'm using them less an less. > > > > > > > > > > > > 3. Pivot the project - this is a whole bike shed argument in itself. > > But > > > > if > > > > > > people are interested in still hanging out (I am) but have other > > > > > > things > > > > > > they're interested in. If you like this, either vote for something > > you've > > > > > > seen or recommend a new thing. I will volunteer donating > > > > > > https://github.com/aboriginal-armadillo/coe-webui/ it's a webui that > > > > hosts > > > > > > a whole galaxy of other LLMs. I want to emphasize that is not > > > > > > option 3- > > > > > > option 3 is doing _something_ else, and please volunteer ideas- > > > > > > that is > > > > an > > > > > > idea/thing I volunteer. > > > > > > > > > > > > or > > > > > > > > > > > > 4. I'm watching/interested, but not voting. > > > > > > > > > > > > Thanks for your time! > > > > > > > > > > > >
