On 2020-08-03 09:47, Jochen Theodorou wrote:
> On 03.08.20 07:57, Paul King wrote:
>>
>> Hi everyone,
>>
>> The GContracts project (design-by-contract extension for Groovy) has
>> been archived:
>>
>> https://github.com/andresteingress/gcontracts/
>>
>> I believe there is sufficient merit in the functionality it offers for
>> us to consider taking up support of the codebase, and the project owner,
>> Andre Steingress, is happy for that transition to take place.
> 
> I think there are some regulations to follow from the ASF side. Since
> you and Andre are the sole committers it should not be too difficult.
> Best of course would be if Andre would be a Apache member, then we could
> do this as simple code contribution
> 
>> We could try to re-invigorate GContracts outside the ASF but I think our
>> community where a larger pool of folks can contribute when they have
>> availability makes more sense than another single person trying to take
>> it over and then potentially running out of steam down the track.
>>
>> We could give it it's own repo and have it as a subproject but for now I
>> think it is easiest just to have it as an optional module in the core
>> repo (targeting Groovy 4). In the PR, I have marked the main annotations
>> as @Incubating for the time being. For further details, see here:
>>
>> https://github.com/apache/groovy/pull/1337
>> https://issues.apache.org/jira/browse/GROOVY-9671
> 
> +1 except... would this loose the history? That would not be nice.

I have no practical experience with gcontracts, but I agree that the
history could be useful to track some further issue with the module.

I wonder, how problematic the merge was? It is was mostly "change
package" and "move" refactor, maybe it would be good to do the fetch of
external repository of gcontracts as an another remote repo, then do the
changes in a separate branch and merge that branch into master via PR
(preserving the history)?

Nevertheless, it still generates some extra work.

Marcin

-- 
https://blog.solidsoft.pl/ - Working code is not enough

Reply via email to