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 MOJAVE

platform::shell

platform::shell(n)					       Tcl Bundled Packages						platform::shell(n)

__________________________________________________________________________________________________________________________________________________

NAME

       platform::shell - System identification support code and utilities

SYNOPSIS

       package require platform::shell ?1.1.4?

       platform::shell::generic shell
       platform::shell::identify shell
       platform::shell::platform shell
_________________________________________________________________

DESCRIPTION

       The platform::shell package provides several utility commands useful for the identification of the architecture of a specific Tcl shell.

       This  package  allows the identification of the architecture of a specific Tcl shell different from the shell running the package. The only
       requirement is that the other shell (identified by its path), is actually executable on the current machine.

       While for most platform this means that the architecture of the interrogated shell is identical to the architecture of  the  running  shell
       this  is  not generally true. A counter example are all platforms which have 32 and 64 bit variants and where a 64bit system is able to run
       32bit code. For these running and interrogated shell may have different 32/64 bit settings and thus different identifiers.

       For applications like a code repository it is important to identify the architecture of the shell which will  actually  run  the  installed
       packages, versus the architecture of the shell running the repository software.

COMMANDS

       platform::shell::identify shell
	      This command does the same identification as platform::identify, for the specified Tcl shell, in contrast to the running shell.

       platform::shell::generic shell
	      This command does the same identification as platform::generic, for the specified Tcl shell, in contrast to the running shell.

       platform::shell::platform shell
	      This command returns the contents of tcl_platform(platform) for the specified Tcl shell.

KEYWORDS

       operating system, cpu architecture, platform, architecture

platform::shell 						       1.1.4							platform::shell(n)