Project

General

Profile

Support #262

Play with GIT

Added by John Abbott over 11 years ago. Updated about 1 month ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
Various
Target version:
Start date:
10 Oct 2012
Due date:
% Done:

10%

Estimated time:
Spent time:

Description

Anna & John: Use a temporary copy of CoCoALib to learn the various GIT commands.


Related issues

Related to CoCoALib - Feature #215: Janet Bases: check and include code in CoCoALib (first prototype)Closed2012-08-02

History

#1 Updated by Christof Soeger over 11 years ago

I used some of the ideas from
http://undefinedvalue.com/2010/07/02/workflow-remote-cvs-local-git
to use git on my side.

But you probably want to use git-cvsimport to create the initial git repository, that will import also the history from cvs.

#2 Updated by Anna Maria Bigatti over 11 years ago

  • Category set to Administration

Now we have a git copy of cocoalib to play with.

Moreover I tried to make a new small project (math exercises ;-) to practise on, but we need a server with git (now on "cocoa") and user accounts, and a "group".
(now "cocoa" has only one user)

#3 Updated by Anna Maria Bigatti about 7 years ago

  • Project changed from CoCoA to CoCoALib
  • Category changed from Administration to Various
  • Target version set to CoCoALib-1.0

This issue was under "CoCoA" instead of "CoCoALib".
I'm recovering these old and forgotten issues, so we reconsider them.

#4 Updated by John Abbott over 2 years ago

  • Target version changed from CoCoALib-1.0 to CoCoALib-0.99850

Florian and Bernhard suggest putting the source on Github/Gitlab.

#5 Updated by John Abbott over 2 years ago

Does anyone have useful experience to help decide between Github/Gitlab/other? And also how one goes about in practice?

#6 Updated by John Abbott over 1 year ago

  • Target version changed from CoCoALib-0.99850 to CoCoALib-0.99880

#7 Updated by John Abbott about 1 month ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

I am strongly tempted to postpone this until after we reach version 1.0.

Pros: putting the sources on GitHub (or similar)
  • would increase the visibility of the CoCoA project
  • would make it easier for others to contribute to CoCoA
  • might give us a "back-up" independent of our usual computers
Cons:
  • someone needs to consider all "pull requests" (i.e. contributions via GitHub)
  • not really necessary for a project with few developers
  • could in principle open CoCoA to a sort of "xz" attack
  • we would have to learn how to use git/GitHub (git can be quite awkward at times)

Also available in: Atom PDF