~sircmpwn/writefreesoftware.org

1

Guides for writing good software in scope?

Otto Richter (Codeberg e.V.) <otto@codeberg.org>
Details
Message ID
<b0bbb0631cedb0b630754ee8552a3f4a63b24050.camel@codeberg.org>
DKIM signature
pass
Download raw message
Hi all,

I'm currently considering to expand the Codeberg Documentation with the
following content, and I'm thinking it might be a good fit for
writefreesoftware.org if you think it is in scope.

The mailing list doesn't appear to be super active, so I'm not sure if it makes
the most sense to submit articles here, or publish them somewhere else (and get
quicker feedback), and finally propose to copy them here.

It is basically about guiding people to a successful Free Software project after
they wrote the first few lines of code. Ideas for articles and content includes:


Localization: How it can work, what to think of in early stages, best practices
and tools.

Accessibility: Especially for web projects, I'll probably get a little biased
and promote semantic HTML, because it gives you accessibility out of the box. I
recently learned some things about accessibility in the context of Forgejo, and
there are some cool things I'd like to share.

UX / User Research: I'm currently doing a lot of user research and testing for
Forgejo, and I'd like to encourage more projects to do the same. I learned a lot
about our users, and in my eyes there's a lot of potential to optimize free
software by applying some patterns here ...

Sustainability: How to develop software with less impact on the environment
during the development process.

Contributor workflow and community building: How not to work alone, how to build
decision making processes etc.

Funding: Different models on how to compensate for the effort, and the (dis-
)advantages of them



Topics I likely won't cover on my own, either due to lack of expertise or time,
but that might still fit in the pattern above:

Performance: Things to avoid when you want to scale up your software.

Maintainability: How to build a codebase that is fun to work with in two years
or more.


Let me know what you think!
Kind Regards
Otto Richter
Codeberg e.V.



-- 
https://Codeberg.org
Codeberg e.V.  –  Arminiusstraße 2-4  –  10551 Berlin  –  Germany
Registered at registration court Amtsgericht Charlottenburg VR36929.
Details
Message ID
<D0P4Y6KYHQNV.1P4RBQSFHPSQ@cmpwn.com>
In-Reply-To
<b0bbb0631cedb0b630754ee8552a3f4a63b24050.camel@codeberg.org> (view parent)
DKIM signature
pass
Download raw message
Hi Otto!

On Sat Apr 20, 2024 at 7:34 PM CEST, Otto Richter (Codeberg e.V.) wrote:
> I'm currently considering to expand the Codeberg Documentation with the
> following content, and I'm thinking it might be a good fit for
> writefreesoftware.org if you think it is in scope.
>
> The mailing list doesn't appear to be super active, so I'm not sure if
> it makes the most sense to submit articles here, or publish them
> somewhere else (and get quicker feedback), and finally propose to copy
> them here.

FYI this mailing list is mostly devoted to the practical processes of
maintaining the documentation, which is to say patches and translations
and technical discussions pertraining to, like, the git repo. And the
website is mostly good to go so that doesn't require much activity.

That said... we have a forum now!

https://discourse.writefreesoftware.org

It might be smart to open a thread there? That could also be a good
place to solicit feedback on drafts and such.

Responding here for now, I think a lot of the stuff you have in mind is
(1) a great idea, (2) can and should be facilitated by
WFS-the-institution, and (3) does not exactly fit with WFS-the-website.

I wonder if it makes sense to have separate websites (or areas of the
same website) for what we have now, retroactively categorized as
"theory", and what you have in mind, proactively categorized as
"practice" or "praxis"?
Reply to thread Export thread (mbox)