Hi,
This is a gentle reminder that the deadline for submitting your proposals
is tomorrow.
btw, we are expanding our reach including members of the eclipse-dev
mailing list.
So, if you know someone who might be interested in this contractor
position, please forward this message to them or let us know so we can
reach out directly.

Thank you and Best Regards,

Thomas Froment
Eclipse IDE Program Manager | Eclipse Foundation Europe GmbH
💬 @thomas.froment:matrix.eclipse.org <https://chat.eclipse.org/> |  X
<https://twitter.com/tfroment> | LinkedIn
<https://www.linkedin.com/in/tfroment/>


On Wed, Mar 27, 2024 at 5:20 PM Thomas Froment <
thomas.from...@eclipse-foundation.org> wrote:

> Hi,
>
> The Eclipse IDE Working Group would like to fund a consultant to help grow
> the base of contributors and committers on the Eclipse IDE related
> projects. You will work in support of the Eclipse IDE Working Group
> community of developers, contributing projects, and the wider Eclipse IDE
> community with a focus on onboarding newcomers and helping other
> contributors as well as fixing and reviewing issues that affect the wider
> Eclipse IDE ecosystem.
>
>
> This role will work within the Eclipse IDE related open source projects
> and collaborate alongside the Eclipse IDE Working Group Steering Committee,
> Planning Council and Eclipse Foundation Staff, and others supporting
> individuals to grow the user and technical community around the Eclipse IDE.
>
>
>
>    -
>
>    This prioritized development effort is to ultimately grow the number
>    of Committers, in cooperation with the program manager:
>    -
>
>       Welcoming new potential or existing contributors, triaging and
>       responding to incoming Pull Requests on a daily basis,
>       -
>
>       Helping them get process items resolved (like ECA, version bumps,
>       matching documentation, API, etc.),
>       -
>
>       Responding to emails on dev lists or messages on slack or matrix
>       rooms that require attention or direction to a more suitable location,
>       -
>
>       Introducing new contributors to the community to increase
>       acceptance from existing committer groups,
>       -
>
>       Writing / improving contributor documentation, ensuring  the
>       resources are easy to locate,
>       -
>
>       Preemptively going through issues and community forums, helping
>       people out where they can, and pointing them to materials that can get 
> them
>       set up properly and smooth the developer experience of their workflow,
>       -
>
>       Providing resources to bootstrap new contributors, recording
>       "hands-on" videos showing potential new arrivals how to get started as a
>       new contributor in the community, speaking as a presenter in webinars,
>       posting “how-to” blogs, hosting virtual drop-in office hours,
>       -
>
>       Analyzing the contribution pathways, engagement styles, and other
>       elements of the contributor experience in Eclipse IDE-related projects 
> and
>       optimizing them to:
>       -
>
>          help both active full-time contributors and new or part-time
>          contributors have a positive experience and as few barriers to 
> quality
>          contribution as possible,
>          -
>
>          notice when issues are recurring and create resources that
>          clarify or solve these issues
>          -
>
>          add multiple pathways for contributor onboarding - for example,
>          targeted week-long fast paced contribution clinics…
>          -
>
>    Desired Skills and Experience
>    -
>
>       Committer on one or more Eclipse IDE projects;
>       -
>
>       Experience with the Eclipse IDE as an end-user;
>       -
>
>       Experience with the Eclipse Development Process
>       <https://www.eclipse.org/projects/dev_process/>;
>       -
>
>       Experience with the Eclipse IDE Simultaneous Release
>       <https://projects.eclipse.org/releases>;
>       -
>
>       Experience in community development or related field;
>       -
>
>       Knowledge of GitHub, Gitlab, or any other code and issue management
>       system.
>
>
> If you are interested, please reach out to me as a next step and provide
> some information as a first step:
>
>    -
>
>    Identification of who will perform the work,
>    -
>
>    A short overview of your experience and participation in those
>    projects,
>    -
>
>    A proposed price on an ongoing base,
>    -
>
>    A rough estimate how much time (hours per week) you would be able to
>    commit to this initiative
>
>
>    -
>
>    See issue #19
>    
> <https://gitlab.eclipse.org/eclipse-wg/ide-wg/ide-wg-dev-funded-efforts/ide-wg-dev-funded-program-planning-council-top-issues/-/issues/19>
>    for more information.
>
>
> Please let me know by Thursday, April 11th if you are interested in
> pursuing this opportunity. Also, I would be happy to answer any questions
> you might have, either by direct email, matrix chat or zoom call.
>
> Best Regards,
>
> Thomas Froment
>
> Eclipse IDE Program Manager | Eclipse Foundation Europe GmbH
>
> 💬 @thomas.froment:matrix.eclipse.org <https://chat.eclipse.org/> | X
> <https://twitter.com/tfroment> | LinkedIn
> <https://www.linkedin.com/in/tfroment/>
>
> Eclipse Foundation <http://www.eclipse.org/>: The Community for Open
> Collaboration and Innovation
>
> References - Eclipse IDE Working Group with their Dev Effort Initiative
>
>    1.
>
>    Helping to Assure the Future of the Eclipse IDE
>    <https://eclipseide.org/working-group/development-funding-initiative/>
>    2.
>
>    EclipseCon's community day presentation
>    
> <https://docs.google.com/presentation/d/11sUXGkNGfxgTg5dKkDzCcm5-UaanwGqk7siRMfy1heA/edit#slide=id.g16c3c3d0ade_0_0>
>    3.
>
>    Guidelines for Management of Working Group Funded Development Efforts
>    and Initiatives
>    <https://www.eclipse.org/org/workinggroups/wgfi_program.php>
>
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to