[
Date Prev][Date Next][
Thread Prev][Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [scava-dev] Terminating Eclipse Scava
|
Hiho wonderful people,
Thank you for the kind answers! It's a pleasure to hear from you two as well. :-)
I will proceed with the termination then, which you can follow in this issue [1] for public scrutiny and feedback.
[1] https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/1208
Your inputs might be needed at some point to acknowledged the termination, I'll let you know if and when.
Eclipse projects and repositories are indeed indexed by the Software Heritage crawlers. However, as you may know, indexing (or updates) might take time, as there are hundreds of millions (!) of projects registered there. So it's always better to double check, and yes, they have our repos [2].
[2] https://archive.softwareheritage.org/browse/search/?q=eclipse+scava&with_visit=true&with_content=true
Also, by any chance, do you know who owns the crossminer.org <http://crossminer.org/> domain name?
Thank you, have a wonderful day! :-)
—
Boris Baldassari
Open Source Consultant | Eclipse Foundation Europe GmbH
M:+33 648038289
> Le 9 juin 2026 à 07:33, Jurgen Vinju via scava-dev <scava-dev@xxxxxxxxxxx> a écrit :
>
> Dear Boris
>
> Nice to hear from you! I hope we can meet again sometime. Archiving is the natural thing to do from CWI's perspective too. Like Davide said.
>
> We do have the requirement to keep websites and GitHub projects alive in a static archived state. So I was happy to read that this is possible. These projects contribute to all our portfolios when working on the next proposal. Also we still learn from the code often (some of it is nowhere else)
>
> Let us know if you need help for the archival or the termination review. Is scava already on softwareheritage.com?
>
> Merci!
>
> Jurgen
>
> Jurgen Vinju
> - CWI
> - TU Eindhoven
> - SWAT.engineering
> http://jurgen.vinju.org
>
> On Tue, 2 Jun 2026 at 09:46, Boris Baldassari via scava-dev <scava-dev@xxxxxxxxxxx> wrote:
> Hiho good people,
>
> This is a friendly message from the Eclipse Management Office (EMO) to request feedback and, hopefully, reactions, regarding the possible termination of the Eclipse Scava project [1].
>
> [1] https://github.com/eclipse-scava
>
> There has been no activity since many years -- in 2019 for the mailing list [2], and 2020 for commits, see [3].
> Our usual procedure for inactive projects is to ask for feedback and recommendation from the project team and/or its users, if any, to see if it is still used and maintained. If so, we are happy to set up a Progress Review [4], set up new elections, and make everything possible to help new developers to get onboard. If not, we will create a termination review [5] to archive the project. Please also note that archived projects are not deleted and can easily be revived if any party wishes so.
>
> [2] https://www.eclipse.org/lists/scava-dev/
> [3] https://grimoire.eclipse.org/app/dashboards?security_tenant=eclipse#/view/Overview?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-8y,to:now))&_a=(description:'Overview%20Panel%20by%20Bitergia',filters:!(('$state':(store:appState),meta:(alias:'Empty%20Commits',disabled:!f,index:git,key:files,negate:!t,params:(query:'0'),type:phrase),query:(match:(files:(query:'0',type:phrase)))),('$state':(store:appState),meta:(alias:Bots,disabled:!f,index:git,key:author_bot,negate:!t,params:(query:!t),type:phrase),query:(match:(author_bot:(query:!t,type:phrase)))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:git,key:cm_pj_id,negate:!f,params:(query:technology.scava),type:phrase),query:(match_phrase:(cm_pj_id:technology.scava)))),fullScreenMode:!f,options:(darkTheme:!f,useMargins:!t),query:(language:lucene,query:'*'),timeRestore:!t,title:'Public%20Overview',viewMode:view)
> [4] https://www.eclipse.org/projects/dev_process/development_process_2010.php#6_3_8_Restructuring_Review
> [5] https://www.eclipse.org/projects/dev_process/development_process_2010.php#6_2_6_Archived:~:text=In%20exceptional%20situations%2C%20such%20as%20projects%20with%20zero%20active%20committers%20or%20projects%20with%20disruptive%20Committers%20and%20no%20effective%20Project%20Leads%2C%20the%20Project%20Leadership%20Chain%20has%20the%20authority%20to%20make%20changes%20(add%2C%20remove)%20to%20the%20set%20of%20committers%20and/or%20Project%20Leads%20of%20that%20project.
>
> Any comment, thoughts, or push back is more than welcome.
>
> Thank you, have a wonderful day!
>
> —
> Boris Baldassari
> Open Source Consultant | Eclipse Foundation Europe GmbH
> M:+33 648038289
>
> _______________________________________________
> scava-dev mailing list
> scava-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/scava-dev
> _______________________________________________
> scava-dev mailing list
> scava-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/scava-dev
