Recruiting for an open source project Post: 302904981

Sponsored Content

Top Forums UNIX for Advanced & Expert Users Recruiting for an open source project Post 302904981 by bakunin on Sunday 8th of June 2014 08:40:40 PM

06-08-2014

Registered User

First off, i have to say, i am interested. I could put together some CV covering what i have done so far, but i think searching through the 4k posts i have here will tell you far better what i can or cannot do. I have already written and maintained shell scripts of 8k lines of code, so i have no problems doing whole applications in shell.

In normal circumstances i would point you to Neo, the forums owner, for how to deal with job offerings but on the other hand i suppose from the "open source" in the first sentence it will be volunteer work anyway, so this is not a "job offering" in a strict sense. There are no clear rules about this and as a border case i am willing to let it stand for the moment.

What makes me wonder is this: you want to create some open source software package. Why do you need formal CVs? I'd say if you find people willing to work for nothing you shouldn't be too picky about who they are. If they cannot code (good enough) or do not have the necessary experience or whatever their lack of qualification may be - it will show soon enough, wouldn't it?

So why don't you - instead of asking people for CVs - just post/submit the code along with some documentation, wishlists, known bugs, specifications, ... and see what happens?

Without wanting to anticipate his decisions and without promising anything: there might be chance that Neo is willing to adopt such a project as an additional board activity. You really should talk to him (he won't bite - not when the moon is not full ;-)). On the other hand, it might be better for the project to use a well-established platform like sourceforge, but having not worked for any open-sorce-projects i can't tell.

Still, it would be interesting to hear more about the projects background and the environment it is foing to take place in. Please elaborate.

bakunin

This User Gave Thanks to bakunin For This Post:

bakunin

View Public Profile for bakunin

Find all posts by bakunin

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Open source project

Hi Guys, This might not be the right place to ask but I want to contribute to some open source project. Can anyone please help me to how to start and where to start?

2. Shell Programming and Scripting

Feedback on "withsome" open source project

I have been developing an open source UNIX project for a few years and am looking for feedback on whether further development of the "withsome" project is of interest to other programmers. One simple example to give an idea of the project is: withsome ./pugs vi Pugs.pm 1)...

LEARN ABOUT DEBIAN

codeeditor

codeEditor(1)						       PythonCard Developers						     codeEditor(1)

NAME

       codeEditor - A Python-aware code editor written using the PythonCard GUI framework

SYNOPSIS

       codeEditor [file] [switches]

DESCRIPTION

       The  codeEditor	program  is  one  of  the tools included with the PythonCard GUI framework.  It is focused on being a simple to use Python
       source code editor.  It is not intended to be a generic editor or replace vi(m), Emacs, etc. If you are already happy  with  your  existing
       editing environment for Python source code, there is no particular reason you have to switch.

       codeEditor  borrows  ideas  and	code  from  IDLE  as  well  as	Mark  Hammond's Pythonwin, PyCrust (the PythonCard shell) and Robin Dunn's
       pyshell.py. The core editor component uses the wxPython wxStyledTextCtrl (wxSTC) which in turn uses Neil Hodgson's  Scintilla.  Isn't  open
       source fun? In 15 minutes you can have a pretty decent editor by standing on the shoulders of others.

SWITCHES

       Note that switches must come after any filename in order to be recognized.

       -p     Show property editor

       -m     Show message watcher

       -l     Enable logging

       -s     Show shell

       -m     Show namespace

       -d     Show debug menu

NOTES

       The  codeEditor	utility  also provides additional functionality that is not discussed in this manpage, because it is somewhat difficult to
       completely describe usage of a GUI program in a text-based manpage.  For more detailed usage instructions or for more  information  on  the
       PythonCard  GUI framework in general, you should install the pythoncard-doc package and take a look at the various walk-throughs, tutorials
       and samples included with it.

       Once the pythoncard-doc package is installed, the documentation is installed to /usr/share/doc/pythoncard-doc, and is  also  available  via
       Debian's doc-base infrastructure - find it in the Devel section using dwww(1), doc-central(1) or dhelp(1).

       If you would rather not install the pythoncard-doc package, you can find essentially the same information on the PythonCard website:

       http://pythoncard.sourceforge.net

BUGS

       Although it is considered to be stable, this is still development-level software.  If you use codeEditor as a real text editor then you may
       want to work on backup copies of documents in case there are bugs that might corrupt your text.

       Please report bugs in this or any PythonCard component to the Debian Bug Tracking system using reportbug(1).

AUTHOR

       This manpage was written by Kenneth J. Pronovici <pronovic@debian.org>, for use by the Debian project.  Content was  based  on  previously-
       existing PythonCard documentation in other forms.

SEE ALSO

       resourceEditor(1), findfiles(1),

PythonCard GUI Framework					    August 2003 						     codeEditor(1)