Open Source Ecology Forums

elifarley

Hi Elifarley, zach dwiel suggested setting up git on the ose server. Do you think it would be useful?

---------- Forwarded message ----------
From: "Zach Dwiel"
Date: Jan 20, 2013 9:31 AM
Subject: Re: CEB Press Code
To: "Yoonseo Kang"
Cc: "James Wise" , "William Neal"

I think we can have links on the wiki to the code no matter if the
code is in the wiki itself or on an external resource like github.
Also, if there are multiple incompatible versions of the CEB control
code, then we can have multiple versions in git or on the wiki.
Multiple versions and version control/storage medium are completely
independent.

Also, if we aren't comfortable using an external site for hosting, it
is trivial for anyone with sysadmin experience to setup git on a
server, perhaps even the same server running the OSE wiki.

I would gladly setup the version control system (github or other) if I
am assured that it will actually get used. I would also be willing to
use a google hangout and show whoever is interested how to use
git/github from Ubuntu.

cooperatively,
zach

On Sat, Jan 19, 2013 at 11:32 AM, Yoonseo Kang wrote:
> If we're githubbing, then we could put github links on the wiki so that we
> have some inter-database connections.
>
> If we're wiki'ing, then we could have multiple links for different types of
> CEB control code depending on what features are in it, such as with pressure
> sensors or hall effect vs mechanical contact sensors.
>
> Just a few thoughts.
>
> Regards,
>
> Yoonseo
>
>
> On Sat, Jan 19, 2013 at 7:27 AM, Zach Dwiel wrote:
>>
>> nice. I guess what I am most interested in is making it easier to
>> contribute to the OSE code.
>>
>> github.com/ose is way out of date, and all of the real work that is
>> going on is just getting uploaded periodically to the wiki. There is
>> a good reason why every open source software project uses a source
>> control system like github to keep track of things. I could upload my
>> latest changes to the wiki and overwrite the code that is there, but
>> that makes it very difficult for other people who are using the code
>> to see what changes I made and proofread and understand those changes.
>> Maybe I just need to be comfortable uploading my code on the wiki and
>> overwriting the existing version, but I have the feeling that it would
>> wind up seriously inconveniencing someone.
>>
>> What do you guys think is the easiest way for us to collaborate on CEB
>> code?
>>
>> zach
>>
>> On Fri, Jan 18, 2013 at 11:50 PM, James Wise wrote:
>> > heres the stuff i found http://opensourceecology.org/wiki/OSE_on_GitHub
>> >
>> > apparently at github.com/ose you can become a member somehow, not really
>> > sure what that does.
>> >
>> > also started a page to list torrent files but i only really found one.
>> > maybe
>> > will be used more in the future.
>> >
>> >
>> > On Fri, Jan 18, 2013 at 8:58 PM, Zach Dwiel wrote:
>> >>
>> >> Ah yeah, sorry I meant to email yoonseo - he is the one I saw editing
>> >> the code on Jan 15th. I can push that code onto github, no problem,
>> >> just want to make sure the effort is coordinated before I waste my
>> >> time.
>> >>
>> >> What do you guys think?
>> >>
>> >> On Fri, Jan 18, 2013 at 9:35 PM, James Wise wrote:
>> >> > hey zach. i might not be the guy that worked on the code. but i do
>> >> > want
>> >> > to
>> >> > help you sort out getting the official code on github so versioning
>> >> > can
>> >> > happen. i think tonight ill try to find as much ose stuff on github
>> >> > and
>> >> > just
>> >> > list it on the wiki under general github stuff and then from there
>> >> > copy
>> >> > onto
>> >> > the ceb controller page all the different forks and stuff.
>> >> >
>> >> > i just searched github on the wiki and ose on github and theres all
>> >> > sorts of
>> >> > stuff that i know is not listed anywhere.
>> >> >
>> >> > here someone sorta started something official two years ago :P
>> >> > https://github.com/OSE/ceb-controller
>> >> >
>> >> > yoonseo says this the most up to date
>> >> > http://opensourceecology.org/wiki/File:CEBOperationTest.ino
>> >> > http://opensourceecology.org/wiki/CEB_Press_Control_Code
>> >> >
>> >> > is it possible to post that code onto that older ose github page? im
>> >> > not
>> >> > super familiar.
>> >> >
>> >> > what do you think?
>> >> >
>> >> >
>> >> > On Fri, Jan 18, 2013 at 7:48 PM, Zach Dwiel wrote:
>> >> >>
>> >> >> Hey, I was wondering if you'd seen the code I wrote for the CEB
>> >> >> Press
>> >> >> here: https://github.com/dwiel/ose-cebpress-controller-board
>> >> >>
>> >> >> I've got a pause button working as well as pressure sensor control
>> >> >> working.
>> >> >>
>> >> >> I see you've recently worked on the code that is uploaded to the
>> >> >> wiki,
>> >> >> and was hoping we could merge our code at some point so we don't
>> >> >> duplicate work. At the very least, having the 'official' code on
>> >> >> github or something similar that provides real version tracking and
>> >> >> everything would be really nice.
>> >> >>
>> >> >> Let me know if there is anything I can do to help out with this
>> >> >> process.
>> >> >>
>> >> >> zach

elifarley

I guess it's easier if we use GitHub (or BitBucket) instead of installing it on OSE's server, is that ok?

We could then set up a cron job to make backups of the code, in case GitHub disappears someday.

I've added dorkmo and Yoonseok (Yoonseo, is that you?) to GitHub's CEB repository. Should I add anyone else?

zdwiel

I think it would be easiest to use github/butbucket so that we get an easy web front end for people who don't know git. Also, no extra croned backups are necessary by the vary distributed nature of git, everyone who has a copy checked out, has a backup of the entire history. The only event that a croned 'backup' of the repo would be helpful is if there isn't a single person who is using the git repo ...

There were some features that were requested a while back a Pause button being the most significant that I would like to contribute. I can do a pull request if yall are comfortable with that, or if you add me on github, I'll put up some of my code myself.

elifarley

@zdwiel: just added you, thanks!

Beluga

What about installing gitorious http://gitorious.org/

markvdb

Yes, PLEASE put this up on github! Advantages:

* visibility! a project on github gets exposure (and faster search engine credibility)
* free for open source projects
* zero maintenance
* easier for the less (software) technically inclined
* file creation from the web interface
* a growing platform (extra services?)
* wiki functionality (if you want it, can be cloned to other places, so no loss of independence)
* issue tracker

Mark

eBell

My Vote is for github... I'd like to build a CEB press controller to trade with someone who can build the mech/hydraulics, but am unsure as to the most updated version.

Quick Question for Dorkmo et al, the plans at http://opensourceecology.org/wiki/CEB_Press/Manufacturing_Instructions/Detroit_Fab_Lab_Solenoid_Driver_v2 are very different than what Yoonseo was doing here http://opensourceecology.org/wiki/CEB_Press#Electronics_-_CEB_Press_IV 

Is the Detroit version obsolete? Is manual etching no longer the way to go?

Beluga

I understand Gitorious is technically superior to GitHub. I am interested in your views on this. I'm not much of a coder or juggler of versions myself, but I have a basic understanding of version control navigation, diffs etc..

markvdb

Beluga, I can't really see a way in which gitorious would be technically superior to github. Would you care to elaborate on that?

Beluga

I can't really elaborate on that, because I have a very superficial level of understanding in these matters as I'm a non-coder and was expecting someone more knowledgeable to comment. Here's an interesting comparison, which includes GitLab: http://www.boxuk.com/blog/a-tale-of-three-git-systems

eBell

I am strongly in favour of github for any OSE project, primarily due to the similar values, a very visible public repo and a large developer audience. Pretty much exactly what markvdb said up there.

dorkmo

i think yoonseo has been aiming for making the design simple to make since we had issues with etching boards and circuit mill is a whole nother challenge.

on the other hand zach designed a single board sollution using a teensy arduino dip.

trade offs either way. we're definitely better off with more options tho eh. and without git versioning or super clear wiki pages stuff gets confusing, so im glad we're talking about this lol

ps i know theres not much development value but i think itd be cool to make our own copper clad boards

eBell

Thanks for the clarification.

While I think it's important to have multiple 'forks' depending on what resources are available, I still think it's really important to have an indication of what the latest 'stable build' is. If I want to go ahead and build the CEB controller and donate it to a metal fab build, I want to know it will work.

Since there are multiple sensor platforms being used (hall effect, magnets, etc), is there any indication what is the 'best' yet?

jesspinto

That would be great. But how is ubuntu different. Could you give a few bullet points.

Agile methodology

Howdy, Stranger!

Categories

In this Discussion

Open Source Ecology Forums