We have yesterday applied to https://hub.fosstodon.org/ for an account in Apache Airflow. And I encourage others who are interested to make their own choice and do the same for their PMC.
My personal opinion is that such a discussion makes very little sense if the goal is "let's get a centrally managed solution first" before we even know if that makes sense and where our users are and how the situation evolves. Mastodon makes it relatively painless to migrate between servers if needs be - https://blog.joinmastodon.org/2019/06/how-to-migrate-from-one-server-to-another/ - this the whole point of federation approach, if you do not like the moderation and COC you get at one server, you move and you bring your users with you (if they concur). IMHO It's far better if each of the individuals who are interested to run Mastodon, will do it on behalf of their PMC, just try it and apply at the server of their choice. Let's gather experiences and see what works. If we find that we need an Apache run server and have good rationale behind it, we might decide to do it (or not). And I think it's far too early (if even at all) to expect INFRA to do anything about it on the central level or get a server that one of the ASF members will run for all the PMCs. On a philosophical level - I personally believe trying to centralise the approach is also pretty much 100% against the whole idea of federation. The federation is not there to "centralise" the approach, but to make it easier to distribute it and the ASF is VERY well prepared for that distributed world. The PMC independence and self-governance except very, very few central services and really important aspects (like licensing. release policy and publishing) is precisely what federation idea supports. And federation means that at the PMC level you have both the benefit of choosing the server as well as the responsibility to make the choice and bear the cost of setting up/managing and moderating. It looks like centralization is an attempt to reap the benefits of decentralisation without bearing the cost of managing it. Somehow it does not click to try to centralize it back. J. On Tue, Nov 8, 2022 at 2:30 AM Peter Hunsberger <peter.hunsber...@gmail.com> wrote: > > On Mon, Nov 7, 2022 at 1:28 PM Gary Gregory <garydgreg...@gmail.com> wrote: > > > Then why not just keep using Slack? > > > > Mastodon would let you federate to the rest of the outside world. It > could let the ASF tell the world that some group of people (coming from the > Apache Mastodon server) have been vetted by us. Vetted could range > somewhere from "has an apache.org email" to approved by the board > somehow.... (We could do both with two different servers.) > > Peter Hunsberger > > > > Gary > > > > On Mon, Nov 7, 2022, 14:17 Niels Basjes <ni...@basjes.nl> wrote: > > > > > Yes, normally it is a lot of work for moderating. Hence my proposal to > > > limit it to (initially) only projects (pmc). > > > > > > By doing that I thought to eliminate the need for additional moderation. > > > > > > Niels > > > > > > On Mon, 7 Nov 2022, 18:00 Peter Kovacs, <pe...@apache.org> wrote: > > > > > > > Hi Niels > > > > > > > > Am 07.11.22 um 12:58 schrieb Niels Basjes: > > > > > I'm sorry to admit I don't have the skills to keep something like > > this > > > > > running reliable at this scale. > > > > > > > > I think you speak tech skills. I guess we would need moderators, and > > > > mentors for projects. > > > > > > > > Social media / Mastodon is not only about tech. It is about community, > > > > isn't it? > > > > > > > > > > > > > > Niels > > > > > > > > > > On Mon, 7 Nov 2022, 12:41 Peter kovacs, <peter.kov...@posteo.de> > > > wrote: > > > > > > > > > >> Hi all > > > > >> > > > > >> @walter > > > > >> I don't think your argument is a good one. > > > > >> If the name is inappropriate then we should change the Domain and > > not > > > > try > > > > >> to stay invisible. > > > > >> However this should be a different discussion. > > > > >> > > > > >> @Niels > > > > >> An own server means work. I think it is only feasible if we get a > > team > > > > >> together that maintains the service. Would you volunteer in case one > > > is > > > > >> build? > > > > >> > > > > >> All the best > > > > >> Peter > > > > >> > > > > >> > > > > >> Am 6. November 2022 23:52:03 MEZ schrieb Walter Cameron < > > > > >> walter.li...@waltercameron.com>: > > > > >>> Hi Niels, > > > > >>> > > > > >>> I don’t think it’s appropriate to further expand the impact of our > > > > >>> improperly > > > > >>> owned domain. Why risk people on social media confusing us with an > > > > >>> Apache organization? > > > > >>> > > > > >>> Gunalchéesh, > > > > >>> Walter > > > > >>> > > > > >>> On Sun, Nov 6, 2022 at 12:20 PM Niels Basjes <ni...@basjes.nl> > > > wrote: > > > > >>> > > > > >>>> Hi, > > > > >>>> > > > > >>>> Given the recent events around twitter I had this crazy idea: > > > > >>>> What if the ASF would run their own Mastodon instance under the > > > > >> apache.org > > > > >>>> domain? > > > > >>>> > > > > >>>> Primarily this would make it possible for all projects to have a > > > clean > > > > >>>> account that can be used for project announcements (i.e. usable by > > > > PMCs > > > > >> ?) > > > > >>>> I expect this to also make it quite easy to archive all > > > communication > > > > >> via > > > > >>>> this route. > > > > >>>> Like: > > > > >>>> > > > > >>>> - @a...@apache.org > > > > >>>> - @fl...@apache.org > > > > >>>> > > > > >>>> Second (I consider this to be optional) it would allow all > > > > >>>> committers/pmcs/... to have a clean ASF relatable point of > > > > >> communication. > > > > >>>> In my case > > > > >>>> > > > > >>>> - @nielsbas...@apache.org > > > > >>>> > > > > >>>> I have NO idea how easy/hard/expensive such a thing is at the > > scale > > > of > > > > >> the > > > > >>>> ASF. > > > > >>>> I just wanted to drop the idea here so it can be discussed (and > > then > > > > >> either > > > > >>>> be accepted or rejected). > > > > >>>> > > > > >>>> Curious to hear your thoughts. > > > > >>>> > > > > >>>> -- > > > > >>>> Best regards > > > > >>>> Niels Basjes > > > > >>>> > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
