On Mon, Feb 27, 2017 at 1:13 AM, Alan W. Irwin <[email protected]> wrote: > Hi Ray: > > On 2017-02-26 13:24-0000 Ray Donnelly wrote: > >> 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[...] >> 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. > > > My gut instinct is you already have that large critical mass of users > that could easily support (via their bug reports) a two-tiered rolling > release system where one was more stable than the other. > >> 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. > > > Likely the distinction I made between core team and outside helpers > was not that useful. But I still feel you have a problem with too few > people trying to do too much, but I guess it is possible adoption of a > good CI product would allow you to support a two-tiered rolling > release system with just the present team of MSYS2 developers. > >> 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. > > > Thanks for those references. > > With regard to <https://github.com/msys2/msys2/wiki/Devtopics> I was > interested to find the "Get more people" topic there with comments > that show the MSYS2 developers are just as concerned about that > topic as I am.
I can't speak for everyone but I think having more people to help with the workload would be good. > > However, the MSYS2 implementation of "Get more people" needs some work > in my opinion. For example, that second page you referred to above has > a title of "Contributing to MSYS2", but it actually says nothing about > that topic. Instead it discusses building and creating packages. So > in my opinion that page needs to be renamed (and retitled) "Building > and Creating Packages", and another page created that actually has > specific content about contributing to MSYS2. Please make PRs if you have time. I agree those pages need work. > > Of course, one can infer simply from a comparison of the title with > actual contents of > <https://github.com/msys2/msys2/wiki/Contributing-to-MSYS2> that > building and creating packages does contribute to MSYS2, but the > current situation is (as far as I can tell) that is not explicitly > stated anywhere on the three pages above. > More people writing recipes is good, adding new ones is good but it increases the packaging burden on Alexey. New people coming in and helping out with existing recipes so that the current developers don't have as many to deal with is great. My hope was that more developers from upstream projects would see MSYS2 as a way to satisfy the dire need for good package dependency management and therefore elect to maintain recipes for their projects in MSYS2 directly, but that's not happened as much as I'd like. > > 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 [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
