As a user the only thing I wonder about is if multiblend2 will be the new default instead of enblend. And we could try harder to explain the projection types to the users. And we could add a mosaic wizard. Besides that I cannot complain.
Kind regards, Gunter. Am 7. März 2021 14:16:12 MEZ schrieb yuv <[email protected]>: >On Sun, 2021-03-07 at 09:22 +0000, Bruno Postle wrote: >> currently there is a single person doing code maintenance, >> collecting translations, _and_ doing the releases - these could >> easily be different roles. > >This! What made Hugin great and successful in years past was the co- >operation and co-ordination of the different teams / authors to the >point of trusting and sharing full access to their respective code >repositories; being able to inter-changeably assume the different roles >for the different packages; reaching mutual agreement on repositories >and other tools to use to simplify interchangeability of roles; co- >ordinate releases, bug fixes, etc. > >That co-ordination seems to have gone missing, and re-building it will >require sacrifices and compromises on all ends. > >I have just taken a half-hour stroll down memory lane. The main >comment I have: Why have no admins been added to Hugin / Panotools / >Enblend in ages? My memory fades, but all the names I see are people >that were either there before me, or were added on my initiative. Who >has taken care of the team after I moved on because life? > >* have any new contributors been invited? >* if yes, why have they not accepted the invitation? >* if no, why? >* how many other contributors has the ecosystem missed? not just admins >(the highest level of access/trust). > >Below follow a longish (and incomplete) list of signs of what is in my >view organizational rot. Those signs point to extra work. I am not >asking the exisisting and dwindling team to take on that extra work. I >am saying that the organizational rot is the consequences of the >failure to welcome and embrace new contributors. Who wants to join a >dwindling team who does not welcome change? > >adding team members requires two thrusts: >(a) individuals inspired to become team members, to bring new energy, >new ideas, new code, and eventually change to the projects; >(b) an existing team that is welcoming new contributors and accepts the >change that they bring. > >where are those thrusts? > >And now for the longish list. > >* why are the projects still using Mercurial? IIRC back when the >switch to a unified VCS was made, Mercurial won because it was the one >with most even support amongst operating system (Windows!). Meanwhile, >the landscape has shifted, git is the tool. That would require some >flexibility from all individuals, including Kay (bitbucket? exotic! I >would not adopt it at this time). > >* why are the projects still on Sourceforge? History is past, and they >may have corrected they blunders. But there is no going back and today >Gitlab is the place to be (which would also replace Launchpad, that I >introduced ages ago). > >* it pains me to see F*book promoted on the Hugin's website. Really? >it surely explain less traffic to this mailing list, which means less >potential contributors coming its way. Don't expect an >influencing/advertising tool that has an interest to isolate users into >echo chambers to be a positive to this community. if I was around the >time that decision came up for discussion, I would have vehemently >opposed it. > >* the Enblend/Enfuse website is still... mine! What is the new >generation of contributors waiting to leave their mark? Last news from >five years ago? OK, the tool has matured and no need for new releases, >but someone with a little bit of marketing flair could point out to the >continued flow of Hugin releases, and now to Multiblend, a very >interesting development? > >* the Panorama Tools website list the last new to almost eight years >ago! the latest release tarball is two years ago. > >I could probably find a bunch more, but the point is: encourage new >contributors to take over and replace the current generation and take >this community to its future with as little interference as possible >from us oldies. Else, the community will die when we inevitably do. >So please, please, please, make this a more welcoming place to new >contributions. Kay and Harrie are no newbies, so imagine how difficult >this is for someone who has not been around for that long. The >alternative is to fade into irrelevance, which is why I asked the >thought-provoking question of whether pv is already a replacement to >Hugin. > >-- >Yuval Levy, JD, MBA, CFA >Ontario-licensed lawyer > > >-- >A list of frequently asked questions is available at: >http://wiki.panotools.org/Hugin_FAQ >--- >You received this message because you are subscribed to the Google Groups >"hugin and other free panoramic software" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to [email protected]. >To view this discussion on the web visit >https://groups.google.com/d/msgid/hugin-ptx/0562231dc798a651f9d108242aa2553787bd31d2.camel%40levy.ch. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/0921D4E9-1772-4774-9AF4-C3C8FD06359B%40gmail.com.
