On 3/9/25 16:42, Luke Lollard wrote:
I find email very clunky and slow
Herein lies the beauty and value of email (and IRC) to me.
no, www.gnustep.org is not being replaced by gnustep.github.io . The
latter is being used to make a documentation website using different
tools.
Is this going to be the official location for GNUstep documentation
moving forward? If not, having gnustep.github.io be an official part
of GNUstep is confusing.
The current plan is to move all of the documentation to
gnustep.github.io, and once we feel it is in a ready state to solicit
more feedback on this mailing list. We hope to replace gnustep.org
with gnustep.github.io eventually, but it's possible we might just
keep it as a documentation site.
Should contributors be working on the official website wiki, or the
GitHub site? It seems that all other discussion has been about the wiki.
I would recommend the GitHub site. You can send PRs to
@gnustep/gnustep.github.io. It's built using Sphinx, I think I put the
building instructions in the README but if not I can help you get it
built locally. Alternatively you could push to your fork on GitHub and
enable Actions and Pages for your fork to have GitHub Actions build it
whenever you push.
If you do want to contribute to gnustep.github.io, please reply to my
thread named "gnustep.github.io", not this thread, so we can keep it
organized.
If we do want to improve the wiki, I'd like to see it upgraded to a
newer version of MediaWiki, so that it can look more modern and have
integration of Visual Editor. Either we could try upgrading the current
installation, or using Miraheze or another wiki host (Miraheze is a US
nonprofit that operates several thousand wikis and deals with security,
spam, and upgrades pretty well and consistently, and they have a
close-to-upstream experience unlike sites like Fandom).
I think it would be hard to have something similar; we need to grow a
lot more and it seems that overall documentation quality across the
whole software ecosystem has dropped since the late 2000s/early 2010s,
so even if we ever grow to GNOME-size or KDE-size it might be hard to
get similar documentation quality. But I'd like to imagine that if we
focus on documentation we can be much better than the other
cross-platform frameworks.
Not as difficult as it was to implement the technical achievements of
GNUstep; so it's possible. Sure, it's not as fun as writing the code,
but it's necessary for the project to continue existing and for new
developers to create software using GNUstep.
I agree, documentation should be a key focus right now. It also helps us
find issues that we might not have noticed as active contributors.
A markdown file on GitHub is enough for me, though something a
little more advanced could help us be more efficient.
I think for tracking we should use some collaboratively editable
bullet list, which should probably be either a GitHub wiki or
something on MediaWiki.
Isn't a GitHub wiki essentially a markdown file?
The only value I see of using something more complex than that is if we
could tag tasks by priority, assignee, status, etc., similar to the
tasks already in Savannah[1] (although, it doesn't look active any
more). I know GitHub has a Projects feature, but I've never used it.
I've never used Projects either. I'd like to do something where people
can edit the todo list without having to push commits to GitHub, but we
could just create a new @gnustep/todo repository, let people who
actively contribute but who don't have push access to most projects have
push access to @gnustep/todo, and let people use the web interface to
edit the todo list. But I think the GitHub wiki interface is slightly
better for doing so (I've never used it myself, but I would assume it is
that way, and I've seen a lot of projects manage their todo lists that way).
[1]: https://savannah.gnu.org/task/?group_id=99
[2]: https://github.com/features/issues
