Post by @stefano
I'll probably configure a bugtracker for #littleFedi - collecting bugs, suggestions, etc. will be much easier. I was considering Roundup - what do you think?
Any suggestions?
13 likes
andyc@andyc@yakshaving.social
Jess Robinson@castaway@fosstodon.org
Oblomov@oblomov@snowfan.it
Nicolas Vivier@nicotentin@pouet.chapril.org
6ff334e 💾@6ff334e@littleroko.basilisk.technology
Chris
@chrism@mastodon.bsd.cafe
Savage Forever@foreversavage@mastodon.social
Licorne les ténèbres.@alter_unicorn@masto.bike
Bastianoso Geratewohl@bastian@scheefe.de
EmilioL@Emilio246@mastodon.social
Amin Dost@fluidlogic@oldbytes.space
Internet Deer@Rye@kind.social
PurpleJillybeans
@PurpleJillybeans@kind.social
@stefano@littleone.littlefedi.social can only speak for myself but imho developers expect something like that. Code, commits, issues,.. Haven't used roundup before but yeah, let's try it.
@willi@littlefedi.wurzerfamily.net I know they do. But the littleFedi devs prefer, at least for now, to keep the dev process centralised and release only “when it’s ready”. 😉
Open source is not about doing things the approved way. It is about giving people the freedom to do things another way.
@justin@toot.io we already have forgejo at BSD cafe but the idea is to install a dedicated, bug tracker tool. At least for now.
@stefano@littleone.littlefedi.social @stefano@rpi0w.stefanomarinelli.it I don’t have a preference concerning one solution or the other but I do think that it’s a good idea. Handling everything via Fediverse seems rather chaotic and intransparent to me. I’d love to see what ideas/issues others have.
@stefano you have shephered the littlepeople collective at their own pace and comfort level. I trust your judgment on what feels right for the core team. I know a lot of folks (myself included) would prefer forgejo (especially since federation work is actively happening) but if a standalone bug tracker resonates better, that's good too!
@shom@gts.shom.dev Thank you. A complete CVS system will maybe come in the future but, for now, the LCP want to keep the development cycle in their own control. Spinning up Forgejo (which we're already using at BSD Cafe, so I woudln't need to spin up a new one) would immeidately request a lot of "use it as the others do" and "why isn't the code and entire commit list there?"
So better a separate bugtracker, at least for now :-)