-
Notifications
You must be signed in to change notification settings - Fork 61
Infrastructure Tasks
jacksonh edited this page Oct 6, 2010
·
2 revisions
This is just a list of tasks that don't directly involve hacking on the Manos source code.
- Monodevelop support: It would be nice to have a Manos MD addin that would let you create new projects (manos -init), add new module files, and run manos projects (build + manos -init). I think that would be a great first step.
- Emacs syntax highlighting for templates: I'd love to have better syntax highlighting for the template files in emacs
- suse RPM files: I've done the initial work on creating these files but its blocking on mono 2.8 being released.
- Ubuntu packages: I believe Jo Shields has been sufficiently bribed to do this work.
- openwrap: It would be awesome to have manos deployable as an openwrap package.
- nu: I've created an initial gemspec in manos/release. It works but needs to correctly add manos to the PATH.
- nupack: Would also be nice to support nupack, not sure how this will handle native dependencies though (libev).
- Suse Studio Packaged Project: It would be great to have a Suse Studio project that has Manos (from packages) setup and running. This is obviously blocking on the Suse packages.
- Suse Studio Source Project: More useful for me would be a Suse Studio project that pulls the latest Manos from github, builds and runs it. This would be very useful as an Amazon EC2 image for load testing.
- Linode stackscript: Also very handy would be a Linode stackscript that setups/installs a Manos server. It would be cool if this had git integration too, so people could just push their Manos projects to the server for deployment.
- The build needs some cleanup, I need a better way of updating the version number in the 5 or 6 places it is stored.