Slashdot Mirror
Ask Slashdot: What Does the FOSS Community Currently Need?
First time accepted submitter d33tah writes "In the summer term of my final year of IT's bachelor's course in my university, every student is obliged to develop his own project; the only requirement is that the application would use any kind of a database. While others are thinking of another useless system for an imaginary company that nobody would actually use, I'd rather hack up something the FL/OSS community actually needs. The problem is — how to figure out what it could be?"
Better hygiene. Less beards. More women.
And for that matter, the big social networks and their apps or app-like interfaces. These are two sides to a common threat: the partitioning of the internet into a device- or social network-delineated series of ecosystems.
You should really be thinking of what your course teachers expect from this project. From their point of view they are likely after their students building a basic CRUD program (create, retrieve, update, delete) to show that they understand the basics of designing and implementing a system and have some basic database skills.
The thing is, CRUD programs are not really that interesting or really, that difficult to make. There will be dozens of them available open source, and these will likely cover all the high impact general cases. What you could contribute relatively easily is a a program for a specific case.
For example: I play around with 3D printing, and I have lots of various coloured filament in varying quantities. I want to know how much I have of each so that I can use up the scraps on little prints, and save the longer lengths of filament for bigger prints. At present this means a little guesswork and some time with a tape measure.
This problem could lead to a nice simple project: build a simple database backed system to monitor filament stock levels, which allows putting in info, saying "I have used x much of this spool to print" and asking "which is the shortest spool with enough for this print?". If you kept it to the assumption that it would be a light weight program not requiring an existing database environment that would make it easy to demo as well - jsut use one of those lightweight DBMSs that dumps it's stuff in a single file. Nice and simple, but extensible.
The extensible bit is important, since it means if you get the basics done you can add on some features for extra credit. I don't mean shiny to the user features, but rather shiny to the markers features.
For example: you could make it pseudo distributed, so that I could have it running on two machines independently and synch them at will; this would mean you could look into transaction systems where you store what was done on each and synch them by applying in time order (something that is useful in big commercial database setups such as retail management systems).
Another example: you could have it capable of generating QR code labels linked to the particular spools records, and have a mobile app. Scan the QR code and have the phone call a web service front end to the database and look up exactly how much is left, and offer the option to mark it as printed with.
Basicly: pick something which is simple, but lets you show off your technical skills. If you can help the OSS movement now that's just icing, but you're better off looking after yourself at the moment so that later you can help with less constrained projects.
If you want to learn a lot about code, really help out the community, and get a lot of love, write some documentation for other people's code.
Now how you work the database requirement into that, I don't know. Perhaps you could write a documentation request tracker for ReadTheDocs.org - their site is on GitHub at https://github.com/rtfd/readthedocs.org so you can fork it, write something that lets people request and prioritise projects that need docs, then submit a pull request.
If you're really ambitious, write a web-based environment for writing, editing, and submitting documentation to projects on GitHub, BitBucket, etc.
Wow! You've managed to make programming as much fun as...doing your taxes!
Welcome to the world of real open source software development. It is real work trying to solve real problems of real users. Large projects that would provide real value are never 'fun' - they're a real commitment on the part of the contributors.
From the submitter:
Well, there we go, you already have a problem that needs fixing! So how about this:
A database that keeps track of FL/OSS community needs. Some possible features:
1/ People go to your website/program and input their software needs. Could be a form with relative requirements on each need. You put the requirements and users in a database, with some sort of relationship between user and need.
2/ People with projects can put their project in the database by stating its goals, as well as state of completion. The state of completion implies (negatively) what requirements still need to be fulfilled for each project.
3/ Your fancy program tries by some algorithm to match 1+2, using some sort of database. Your program brings people's needs and the projects needs together in some form that allows the needs to be fulfilled. Bonus points for making it some sort of social site. Your software is not only open source, but even "community driven".
Actually your question points out a need - how about fulfilling that need? You have already tried to find something that would help you, but couldn't find it - how about doing something about it? This is the best way to do software - not by taking an arbitrary list of stuff from others, but actually experiencing the need yourself. Since you know the requirements in some degree, you should put your energies in fulfilling them. Would make an interesting and useful project.
Good luck with whatever you decide to do.