Thread

Does a 3rd year project actually end up being released and maintained? because that looks great, but its gotta be ages away right? i’d love to pay you $50/mo (with others) to make sure you’re invested in it’s future.

Mind you, releasing it as open-source would probably create enough community to keep it going too.

Does a 3rd year project actually end up being released and maintained? because that looks great, but its gotta be ages away right? i’d love to pay you $50/mo (with others) to make sure you’re invested in it’s future.

Mind you, releasing it as open-source would probably create enough community to keep it going too.

Let me just start by saying I understand your concern.

Most 3rd year projects end up dying, but this is something I’ve been wanting to do for a long time, so it’s more then just a project to me 😊
Code freeze is ~10 months time (so yes, quite a long way away) although thats the date imposed by the university, I plan on having something which can be used before then (a cross between a beta and a full release). There will then be a few months of what seems to be no progress as I do all the write up for the projects (15,000 word report) and have exams. So I’m setting myself a target release date as a finished thing ~1 month after exams finish, which gives me time to polish it off and add some stuff which didn’t make it.

And even if I did for some unknown reason (not that I can see that happening) lose interest in this, or heaven forbid rather get a 9-5 office job, I would just open source it so anyone already using it wouldn’t be lost without it.