Hi,
On 3 Nov 2020, at 21:47, Ian Jefferson wrote:
Some good points here:
On Nov 3, 2020, at 4:33 AM, fra...@fraber.de wrote:
- Gradual or "big bang" migration?
Should SVN and GIT run in parallel for some time, or is
it OK to have a single big bang migration? Big bang is
a lot easier…
Big Bang. We are too small and under staffed (current Army of Erich!)
to maintain stuff in parallel. Given the opportunity we can all grab
working copies before the transition. A good thought here Frank.
+1
- Do you want to completely ignore GitHub?
GitHub is the go-to place for open source software.
Google does heavy indexing there. If you want AmForth
to reach a large community, then you have to publish
there. However, it doesn't need to the the primary repo...
Another wise comment Frank. There is something eventually even I
could maintain for the community! Keeping things as open to the main
stream opensource crowd is a good thought even if the day to day is
managed elsewhere and when.
I use both sourcehut and GitHub, I prefer sourcehut but I agree that
amForth should have a presence on Github as well. There are already
various forks of amForth on Github, as well as amForth related code.
Being on Github is important to be visible.
And yes, an automated sync between sr.ht and GitHub could be possible.
A repo on GitHub should be "official", e.g. the same people that run the
main repo (Erich at the moment) should also have control there, even if
someone from the community operates the repo and the sync. This prevents
that the two repos will diverge later.
Greetings
Carsten
_______________________________________________
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel
