Post by @littlefedi_official
As promised, the littleFedi source code will become publicly available in about a week.
We will publish a snapshot of the complete source tree, together with some basic instructions to build and run it. Pre-built binaries will also be provided.
This will not yet be a proper littleFedi release. Documentation still needs work, testing needs to be expanded, and several things need to be cleaned up before we can call it that.
But the important part is that the code will finally be out there.
People will be able to read it, build it, experiment with it, start using littleFedi..
Over time, development will progressively move to the BSD Cafe Forgejo, where we will have the usual tools for issues, contributions, releases and collaborative development.
We're not quite there yet.
For now, the first step is simple: open the doors and let people get their hands on the code.
About one more week.
47 likes
R.L. Dane
π΅
@rl_dane@polymaths.social
Chris
@chrism@mastodon.bsd.cafe
the roamer@the_roamer@mastodonapp.uk
little shom@shom
xenotar@xenotar
Brendan@brendan@social.brendans-bits.com
voipmeister@voipmeister@social.datarek.nl
sm4llth1ng@sm4llth1ng@mamot.fr
Karl Ostendorf@karl@ostendorf.com
Dendrobatus Azureus@dendrobatus_azureus
flo@fasnix
ππ©·π Brett [backup account]@brettm@swarm.coiloptic.org
Flay@flay@fosstodon.org
dch
@dch@bsd.network
Greg Whitehead@grwster@mastodon.social
twm@twm@bsd.cafe
epn4littlefedi@epn4littlefedi
IAintShootinMis@iaintshootinmis@digitaldarkage.cc
Victor GarcΓa π¨π»βπ»πΈπ@vggonz@mastodon.denibol.com
Leonardo Taccari@iamleot@mastodon.sdf.org
^. .^ Paul Wilde@paul@notnull.space
TomΓ‘Ε‘ Odehnal@tomas@odehnal.online
Chuckles@celeduc@mastodon.social
HiMY SYeD - littleFedi@himysyed
Spookybot@teknomagic@todon.eu
fasnix - archiviert@fasnix@fe.disroot.org
Ivor Hewitt@ivor@social.ivor.org
Grunkle Moose@RootMoose@mastodon.bsd.cafe
curl | sudo bash@stefani@kolektiva.social
Chris Bond@Vibracobra23@mastodon.social
@littlefedi_official Congratulations on your progress!
Do you have any idea what license you're planning on releasing under?