Re: [Integrit-devel] Some fixes to integrit

[Ed C. <ec...@no...>]

Thanks, Chris.

This is the first time (I think) that the github area has gotten any
attention other than my own little tweaks.

The sourceforge location is still the authoritative distribution point
for integrit, and it's where the stable releases will go, but github
is going to be great for collaboration and pre-releases.

I think the appropriate place to document that is in the HACKING file.

Yuri, I plan to update HACKING to reflect the use of github for
collaboration.  If you want to fork my repo and update HACKING to
point to your fork as the place to go for collaboration, that's fine
with me.  Otherwise, maybe there's a way for you to get notifications
of pull requests made to my integrit repo---That's github-fu a bit
beyond my skills.  :)



On Mon, Sep 15, 2014 at 3:26 PM, Chris Johns <cb...@vi...> wrote:
> Thanks Ed and Yuri. I've created myself a github account and forked the
> ecashin/integrit project. I'll be pushing my changes to that fork in the
> next day or two once I'm completely happy with them, and then I'll create a
> pull request.
>
> Is there any way that the SourceForge project could be updated just to point
> developers (like me) at the github location instead, or at least let folks
> know that the project on SourceForge is deprecated?
>
> Chris
>
>
>
> On Sat, 13 Sep 2014 20:43:37 -0400
> Ed Cashin <ec...@no...> wrote:
>> Hi.
>>
>>For several years, Yuri D'Elia has been a more active
>>maintainer than
>> me, but I did put integrit on github lately:
>>
>>  https://github.com/ecashin/integrit
>>
>> ... and I did add a fix recently.  It is easy to make
>>releases on
>> github, and it's much easier to collaborate their
>>through pull
>> requests.
>>
>> I suggest that you fork the project on github and send a
>>pull request
>> when you have committed changes that you are happy with.
>>
>> You're right that integrit was created to be simple
>>software that
>> could reach a "done" state and stay there.  I think I
>>didn't really
>> understand, though, that the world expects some minimum
>>amount of
>> updates to be performed on any code base.  It's like a
>>"heartbeat".
>>
>> I still want integrit to retain its minimalism, but
>>changes that make
>> sense are welcome.
>>
>> After a pre-release on github, Yuri or I can make a
>>release on sourceforge.
>>
>>
>> On Fri, Sep 12, 2014 at 4:55 PM, Chris Johns
>><cb...@vi...> wrote:
>>> I have a few fixes/enhancements to integrit, since I'm
>>>considering using it
>>> for a project, and needed to tweak it a little. Should I
>>>send the CVS diffs
>>> out to this list, or what's the best way to get code
>>>reviewed?
>>>
>>> I know that there's been no activity on integrit, and no
>>>new releases, for
>>> about 7 years, which I think is largely due to it being
>>>a pretty stable and
>>> complete tool. However, assuming my changes can go in,
>>>how would a new
>>> release be generated for download from sourceforge?
>>>
>>> Thanks,
>>>
>>> Chris
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Want excitement?
>>> Manually upgrade your production database.
>>> When you want reliability, choose Perforce
>>> Perforce version control. Predictably reliable.
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Integrit-devel mailing list
>>> Int...@li...
>>> https://lists.sourceforge.net/lists/listinfo/integrit-devel
>>>
>>
>>
>>
>> --
>>  Ed Cashin <ec...@no...>
>>
>



-- 
  Ed Cashin <ec...@no...>