30
votes
Ask Tildes: What is the best way to get involved with the development of Tildes?
Hi everyone, I'm a frontend developer and do a bit of backend work as well. I'd really like to contribute some of my downtime to helping build this site. I've checked out the issue tracker on gitlab and some of the docs, tech goals and announcement, but I'd like to start getting my hands dirty and contribute some code.
- Is there a roadmap for development?
- A feature list to implement?
- Bugs to fix?
How can I help out? What's the best way to get started?
Also for all non-devs, what is the best way that they can start helping out?
Great questions and thanks for the showing interest in helping us, we appreciate it.
Gitlab boards will serve as that for us, although we (i.e. me) probably needs to organize it better if we ever get the chance (HALP! invite request overload!). I am also trying to convince @deimos to use Trello as well since their roadmap feature is slightly more fun/marketable.
Our gitlab issues tracker can be sorted by label and the current list of labels and their purpose can be seen here, many of which even non-technical people can help us with, such as suggesting possibilities to investigate and fully fleshed out feature ideas (although please try to make them practical for now).
The best way right now for everyone to help is to just disclose any issues they spot, either by submitting them to our gitlab issues tracker (which I will label properly after you submit them) or make a thread on ~tildes or even ~test which we also monitor for people bug hunting.
Participating in our daily discussions and providing feedback is also crucial and while we can't respond to every single comment, question and concern simply because of how many other things we have to do right now, I promise you we are reading them and taking everything into consideration.
And if you spot anyone asking questions you have seen us answer or address elsewhere, referring to that response for the person will certainly help us a great deal.
We understand our documentation is a bit scattered right now but we're working on that (which you can also help with).
p.s. The reason we aren't opensource yet (@deimos on the HN thread last week):
What made you guys choose Gitlab over GitHub?
Mostly because the
/tildes
url was still available.But seriously, it was mostly because I think GitLab's principles and the way they run their company line up far better with Tildes. They're open-source themselves (GitHub isn't) and overall run the company in a very open way. GitHub doesn't have many feature advantages any more, and they're also way deeper in the VC hole (they've taken $350M) so I'm not sure if they're going to have to start monetizing in some ugly ways eventually.
Yeah, and Sourceforge’s attempt at getting away with inserting adware comes to mind there. :/
I remember hearing about that fiasco. It always seems like there's some kind of arms race between advertisers (and those who use them) with increasingly worse advertising practices and users who are getting increasingly fed up with the tactics that end up being used against them. It's unfortunate because I can't even feel safe enabling basic web advertisements anymore to help support the websites I enjoy using.
Cool, thanks. To be clear, I have no issue at all with Gitlab, I was just curious why one over the other.
I'm not among the initial team, but I use gitlab for my own work. My own personal reasoning for choosing them is pricing (for private projects), tooling available, and disk space provided as distinct advantages over Github.
I think to there are integrations available to sync trello cards with gitlab issues. It might be worth researching.
Thanks, I will definitely look into that since I am the biggest proponent for using Trello. ;)
Added a reminder to do so to gitlab.
No problem. There's no guarantee that existing solutions are sufficient, but a quick glance-over suggested that solutions exist. Unfortunately I can't dedicate much time to researching the issue myself at the moment or I'd just take care of that myself :)
Thanks for the great answer!
Excellent. I enjoy writing documentation. I've just installed pelican and will see where I can help out.
The code repo hasn't gone public yet. We're still waiting for that.
Welcome to the club. We're several already waiting to get our hands dirty :)
I am definitely waiting for you to be able to get your hands dirty on the source code too, given how incredibly reliant I have already become on your Extended ~ scripts. ;)
Well, waiting for it to go Free is probably a prerequisite. Not much to do until then, and a lot of questions will likely be answered by simply looking at the source.
I think the only one who can give you useful information that's not already in the docs or on the issue tracker is @Deimos himself, I'm sure he'll show up shortly :)
My backend dev days are almost a decade behind me, but I've spent that decade in the process design, metrics analysis, service management world. If there is anything I can help with on that end please let me know.