Hi Alan, That list is just the SourceForge users with permissions to the msys2 project at that site and we're moving away from that to be more fully GitHub-based.
The definition of 'core' and 'non-core' isn't something I'm too keen to promote, the other list at http://www.msys2.org/ isn't representative of who actually does the work, and for me, that's what really matters. These days, I'm only an occasional contributor due to time constraints (I will try to be responsive when I can on the packages I'm most familiar with though and anyone can ping me via gmail with any questions about them when they want to), but MSYS2 is very important to me. Alexey Pavlov (obviously), Mateusz MikuĊa, David Macek, Andrea Zagli, and J. Peter Mugaas do more these days than I do. A slightly better list of the core team is probably gotten by running `git shortlog -s -n | head -n10` in each of MINGW-packages and MSYS-packages and merging the output but is still not great because it doesn't count other contributions outside of the package build recipes, people like David Grayson, Martell Malone, Andrew Chadwick, Qian Hong and Renato Silva who help out by answering questions or in upstream projects or with CI systems and also people who bring up these important discussions. It also doesn't give enough credit to newer contributors who are getting more involved which is so important to the future success of the project (Mario Emmenlauer, Alethea Rose, more besides). I could also add a category of people who are attached to other projects that use MSYS2 as the build system or as a source for binary builds (OCD, Gnome, KiCad) but really all contributors and contributions are welcome (and also those of the upstreams, Cygwin, mingw-w64, mintty in particular and also Git for Windows; Johannes Schindelin's work has been very helpful). Apologies if I left anyone out here who feels they should appear, I was tempted to delete this whole paragraph so as not to offend anyone. One thing I would state is that Alexey is the BDFL of this project, and I don't think we could have anyone more suited to that role. Alexey, your continued efforts are hugely appreciated and I reckon that sentiment is felt by everyone here. I know this is getting back to the thread you forked this one from so apologies for that, but personally, I'd like to get to the stage where we have a *really* good CI system, but it needs to be one that Alexey buys into and uses since he does all of the final package builds and uploads. At my day-job a colleague has been working on one based on Concourse CI and, when it's finished I'd like to try to set it up for MSYS2. I know the other CIs have had short-comings (time limits for AppVeyor, 64-bit for TeaCI) and Alexey had concerns that they only operate in isolation, so that after a new package is built they don't test that downstream packages still run or build OK. It'd be nice if PKGBUILDs could list a few representative packages to be run or built after each triggered build I think. Also I'd like to see new nightly installers made and test that they work still (with bisection to figure out what broke it?). Once such a system is in place and good enough we could think about doing a stratified repo layout, possibly where people give +1s on a web UI to say that they used the package from 'testing' in some non-trivial way with the latest of the other ones in 'testing' and it worked fine for them (or -1s if not). But testing repos that aren't used are more harm than good and we need a critical mass of users and contributors to avoid that situation. As for promoting to the core-team, It's not like the core-team as much as it exists get together to make decisions affecting everyone else. There is an IRC channel but I'm not on it these days (I mean to get back to it sometime though). I'd like to hear other peoples' opinions on these matters though, but my hope is that the project is fairly meritoric. On your specific suggestion for a "Want to get involved?" wikipage, we have: https://github.com/msys2/msys2/wiki with subpages https://github.com/msys2/msys2/wiki/Contributing-to-MSYS2 and https://github.com/msys2/msys2/wiki/Devtopics. If you feel they could be better organised then for sure please make some PRs. David Macek moved them from SourceForge to Github recently. Best regards, Ray On Sun, Feb 26, 2017 at 5:14 AM, Alan W. Irwin <ir...@beluga.phys.uvic.ca> wrote: > Hi Ray: > > This post is a change of topic from the current thread concerning > ways of making a more stable version of MSYS2 available to users, > but it is strongly motivated by that thread. > > Right now the total number of admins and developers for the MSYS2 core > team is only 6 according to > <https://sourceforge.net/p/msys2/_members/>, and I believe an > important issue for this project is it needs to recruit more members > of that core team. That expansion of the core team would spread the > load so none of you burn out and also allow dealing with substantial > project improvements (such as making a more stable version of MSYS2 > available to users) which are bound to require a large amount of extra > work by the core team. > > You obviously cannot solve the relatively small size of your core team > in an instant, but to make a start on that you need to evaluate > potential members of that core team. That can be done in a large > variety of ways (most of which you may already be doing). But one > additional way of doing that is to encourage external volunteers with > more mundane potentially crowd-sourced tasks that simultaneuously help > out MSYS2 and also give the current core team a chance to evaluate who > would be useful as additional members of your core team. > > Anyhow, I think it would be potentially a large help to the MSYS2 > project in the long term if you were to write up a wiki page outlining > how external volunteers could help out with the project. My apologies > in advance if such page already exists, and I have just not been able > to find it. > > Alan > __________________________ > Alan W. Irwin > > Astronomical research affiliation with Department of Physics and Astronomy, > University of Victoria (astrowww.phys.uvic.ca). > > Programming affiliations with the FreeEOS equation-of-state > implementation for stellar interiors (freeeos.sf.net); the Time > Ephemerides project (timeephem.sf.net); PLplot scientific plotting > software package (plplot.sf.net); the libLASi project > (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); > and the Linux Brochure Project (lbproject.sf.net). > __________________________ > > Linux-powered Science > __________________________ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
