taskSavannah Administration - Tasks: task #11827, Submission of Condor Framework...


task #11827: Submission of Condor Framework Specification

Submitted by:  Joseph Pesco <condor>
Submitted on:  Fri 17 Feb 2012 01:26:22 PM UTC  
Should Start On:  Fri 17 Feb 2012 12:00:00 AM UTC Should be Finished on:  Thu 18 Apr 2013 05:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Cancelled Privacy:  Public
Percent Complete:  0% Assigned to:  Assaf Gordon <agn>
Open/Closed:  Closed Effort:  0.00

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


( Jump to the original submission)

Mon 25 Aug 2014 03:29:22 PM UTC, comment #11:


I am closing this submission due to inactivity.
You will still be able to register the project again once you have the time to deal with the registration issues.

- Assaf

Assaf Gordon <agn>
Site AdministratorIn charge of this item.
Tue 12 Aug 2014 12:08:00 AM UTC, comment #10:


I'm reviewing old tasks in Savannah.
Are you still interested in the submission of Condor Framework Specification project ?

If within two weeks I still do not get a reply, I will close this submission request.
You will still be able to register the project again once you have the time to deal with the registration issues.


Assaf Gordon <agn>
Site AdministratorIn charge of this item.
Thu 25 Apr 2013 01:36:38 PM UTC, comment #9:

Has Luis left Savannah, or has he moved on to something else at Savannah?

I've reviewed my original notes. Since then I've learned how to map a network resource using nfsd, looked at Ubuntu1, and Google Drive. Google Drive has a Really Simple Syndication feature that is cute.

I've not looked at Git.

yours truly, condor

Joseph Pesco <condor>
Wed 17 Apr 2013 09:23:42 PM UTC, comment #8:

Since Luis leaved Savannah administration, now I will evaluate your submission. Please read comment #3, it contains very exhaustive list of problems with tarball.

Feel free to ask, if you have any questions.

Tomasz Konojacki <xenu>
Project Member
Wed 17 Apr 2013 04:53:00 PM UTC, comment #7:


Just to let you know that I'm leaving Savannah administration, so another person will hopefully continue with your project evaluation.


-Deleted Account- <sirgazil>
Thu 11 Apr 2013 08:50:24 PM UTC, comment #6:


Then, please read comment #3 and we will resume from there.

Should you have any questions, do not hesitate to ask.


-Deleted Account- <sirgazil>
Thu 11 Apr 2013 06:55:32 PM UTC, comment #5:


It's been a very interesting year though. Yes, I am still willing to host my project at Savannah, without hesitation, yes. The tarball I sumitted was mess.


Joseph Pesco <condor>
Thu 11 Apr 2013 03:07:23 PM UTC, comment #4:


I am really sorry about your experience with the project submission process in Savannah. It took Savannah more than a year to review your project, so I apologize for that.

Are you still willing to host your project at Savannah?

If within one week I still do not get a reply, I will remove your project. You will still be able to register it again if you decide to give us another chance.


-Deleted Account- <sirgazil>
Fri 05 Apr 2013 04:59:16 PM UTC, comment #3:

Hi Joseph,

I'm really sorry for the long delay.

While evaluating your project I noticed that you marked it as "Official GNU Software".

If you want your project evaluated by the GNU Eval team, you have to follow a separate process from Savannah. Please see http://www.gnu.org/help/evaluation.html.

If you mistakenly selected the type "Official GNU Software" instead of "non-GNU software & documentation", please let us know and we will evaluate your project for inclusion in Savannah non-GNU.

In any case, I have noticed a few problems in your project that have to be solved before we can approve it.

  • Not all the source files have appropriate copyright and license notices.
  • The source does not include a verbatim copy of the license.

To release your program properly under the GNU GPL, which is the license you indicated in your project submission, you must include a copyright notice and permission-to-copy statements at the beginning of every copyrightable file, usually any file more than 10 lines long. This is explained in http://www.gnu.org/licenses/gpl-howto.html.

In addition, please include a copy of the plain text version of the GNU GPL, available from https://www.gnu.org/licenses/gpl.txt, into a file named "COPYING".

Please (re)read the following documents to get you project approved quickly:


If you are willing to make the changes mentioned above, please provide us with a URL to an updated tarball of your project or attach it to this tracker. Upon review, we will reconsider your project for inclusion in Savannah.

Should you have any questions, do not hesitate to ask.


-Deleted Account- <sirgazil>
Tue 01 May 2012 03:24:55 PM UTC, comment #2:

Hi Folks;

For information concerning Condor Framework Specification try:


Yours truly
"a.k.a. Joseph Pesco"

Joseph Pesco <condor>
Mon 16 Apr 2012 02:53:00 PM UTC, comment #1:

Hi Folks;
I only just found this portion of the Savannah site today! I thought there might have been something in my inbox concerning the tarball considering how badly behaved it is. Work on CFS went on the back burner for a month, or so after submission of the tarball. The specification has grown somewhat since Febuary though, and will be submitted with a more mature tarball.

Yours truly,
"a.k.a Joseph Pesco"

Joseph Pesco <condor>
Fri 17 Feb 2012 01:26:22 PM UTC, original submission:

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.

Registration Administration

While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):

Registration Details

  • Name: Condor Framework Specification
  • System Name: cfs
  • Type: Official GNU software
  • License: GNU General Public License v3 or later (Condor Framework Specification "CFS" Copyright 2012 Joseph Pesco )


CFS is a very lite development enviroment run off the command line, and intentionally uses only the most primative tools as building blocks. CFS does not seek to be a GUI application when it grows up! Revision control is the first pillar of CFS. Also central to CFS is the concept of a the Gufee: a Gross Unique File Exchange Entity. Gross because every file in the CFS tree should have a Gufee, Unique because each file should have it's own unique Gufee, Exchange, because the Gufee is used to track the movement of files (and concepts) as they progress through the development process. The third pillar of CFS is an Incarnation. An, incarnation string kept as a directory, currently located as /opt/cfs/incarnation=< Incarnation String >, contains roughly the following infromation. <Operating system>.<physcial platform>.<Boot Storage Device>.<Installation Date of the Operation System>. Incarnations can be seen at use in the checkin process where each checkin comment is signed by the user with a string comprised of <User's log in name>.<Incarnation String>.<date of check in>. The Gufee is stored in the CFS header information at the top of each file and in rcs describtion in the rcs archive file.

Other Comments:

Dear Sirs;

There are two distinct installation types for CFS. The first is known as a Continuity installation. Root creates a user account known as continuity, and before the Continuity tarball, example provided (though not in the continuity configuration!) the previous continuity user's home directory is DELETED! and the contents of tarball replaces the continuity user's home directory. Continuity is intended as a Cloud Shell Account with the proper implementation. If a network is not available for transport of the Continuity archive file, a flash drive does nicely as a mechanism for transport between two physical machines.

The second configuration, an example provided in this tarball, is a user account directory labeled cfs. I suggest unpacking the tarball into a newly created user account (because the source is not the least bit mature.)

This will install cfs, modify .bashrc, and create ~/bin:

> cd $HOME/projects/cfs/utility

Exit the shell, start a new shell, go to a directory create a RCS directory:

>new_file sample.sh
>co sample.sh

Congradulations you've just created your first cfs complient script file.

I have a to do list that includes a proper specification for a fully developed interface. A central rcs repository rather than a clutter of RCS directories is left as a trivial exersize. (I use: /opt/cfs/repository, though sometimes having the clutter of RCS directories has advantages.)

The installation script is called cfs/utility/install_cfs_II.sh, and creating the Incarnation string is very important and fell out of the script, so you'll have to mkdir -p /opt/cfs/incarnation=<incarnation script>.

I left install_cfs.sh in place in case anyone wants to see first effort. I have primative snapshots implemented though haven't included them here.

Mr. Joseph Pesco
(a.k.a. condor)
351 East 74 Street
New York, NY 10021

-email is unavailable-

Tarball URL:


Joseph Pesco <condor>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by agn (Posted a comment)
  • -email is unavailable- added by xenu (Posted a comment)
  • -email is unavailable- added by sirgazil (Posted a comment)
  • -email is unavailable- added by condor (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follow 10 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    Mon 25 Aug 2014 03:29:22 PM UTC agn StatusIn Progress => Cancelled
        Open/ClosedOpen => Closed
    Tue 12 Aug 2014 12:08:00 AM UTC agn Assigned toxenu => agn
    Wed 17 Apr 2013 09:23:42 PM UTC xenu Assigned toNone => xenu
    Wed 17 Apr 2013 04:53:00 PM UTC sirgazil Assigned tosirgazil => None
    Thu 11 Apr 2013 08:50:24 PM UTC sirgazil StatusPing-ed => In Progress
    Thu 11 Apr 2013 03:07:23 PM UTC sirgazil Should be Finished onMon 27 Feb 2012 12:00:00 AM UTC => Thu 18 Apr 2013 05:00:00 AM UTC
        StatusWait reply => Ping-ed
    Fri 05 Apr 2013 04:59:16 PM UTC sirgazil StatusNone => Wait reply
        Assigned toNone => sirgazil

    Back to the top

    Powered by Savane 3.3