[Alioth-staff-replacement] Notes from the salsa.d.o meeting

[Alexander Wirt]

On Fri, 29 Sep 2017, Olaf Meeuwissen wrote:

> Hi Alexander,
> 
> Alexander Wirt writes:
> 
> > On Fri, 29 Sep 2017, Olaf Meeuwissen wrote:
> >
> >> Hi,
> >>
> >> Alexander Wirt writes:
> >>
> >> > we had a meeting about the status and the next steps of salsa.d.o (git
> >> > replacement). Here are my notes of that meeting.
> >>
> >> Thanks!  Much appreciated.  I have a few questions though.
> >>
> > [...]
> >> > [...] We won't reuse git.debian.org later. It will be turned into a
> >> > readonly archive with the deprecation of alioth.d.o.
> >>
> >> So this means "move someplace else or else" for any git using project on
> >> alioth.d.o, right?
> > Yes. Alioth is deprecated and will be dropped with the EOL of wheezy.
> > [...]
> >>
> >> Any (approximate) ETA on when git.debian.org becomes read-only?  Earlier
> >> mail on this list indicated that nothing would be moved automatically to
> >> weed out inactive projects IIRC, so I'd like to be able to get the SANE
> >> project's affairs in order ahead of time.
> > The timeline we proposed for mailinglists is probably more or less correct.
> 
> I'll dig that up in the list archives then ... no such luck ...
> ... searching for the [sprint minutes][1] ... ah, there it is, I think
> 
>   ## Announcements (wild propasal)
>    * 2017-08-?? communicate the future of alioth and the related services
>      (content: see below "Outline of the future of Alioth")
>    * 2017-08-?? communicate the possible future for mailinglists
>      (see the announcement draft "MailingList-1")
>    * 2017-08-?? communicate the future of version control
>      (see the first draft "VCS-1")
>    * 2017-08-?? announce the new development platform
>      (refer to the wiki documentation (https://wiki.debian.org/Salsa), announcement draft (TODO))
>    * 2017-??-?? notification/reminder: read-only for everything
>      * disable registration
>      * disable project creation
>      * mailinglists reject incoming mail
>      * version control write access is disabled
>      (see the second draft in "VCS - non-git")
>    * 2017-??-?? final note: goodbye alioth
>      (announcement draft (TODO))
> 
> Eh, that's *very* approximate :-| and I am a bit at a loss as to what
> happened with the announcements slated for August.  Did those happen?
> Where?  Can/Will they be sent here as well?
> 
>  [1]: https://gobby.debian.org/export/Sprints/AliothSuccessors2017/Minutes
> 
> > [...]
> >> # I'd much prefer a /sane/ or /sane-project/ instead of /sane-team/ but
> >> # realize quite well that I don't call the shots here ;-)
> > The toplevel group will get a prefix. If being -team, -project or something
> > else isn't finally decided. We don't care if the owners of the toplevel
> > project are DDs or not. You can do whatever you want under your group. Create
> > as many repos as you like or create subgroups that can have other repos.
> > As long as you don't want pages in subgroup projects, you can do whatever you
> > like.
> >
> > Does that answer your questions?
> 
> Somewhat.
https://lists.debian.org/debian-devel-announce/2017/09/msg00004.html

Alex