From f95c187a0fa153a0ca95b6df263b808f7fff4832 Mon Sep 17 00:00:00 2001 From: Hizkiel Date: Wed, 12 Feb 2025 11:37:21 +0100 Subject: [PATCH] update the text on contributerguide.html --- contributerguide.html | 156 ++++++++---------------------------------- 1 file changed, 30 insertions(+), 126 deletions(-) diff --git a/contributerguide.html b/contributerguide.html index 14c68a6..0c7452e 100644 --- a/contributerguide.html +++ b/contributerguide.html @@ -5,129 +5,33 @@
-
-

Contributor's Guide: Writing a Good Proposal

- -

1. Understand the Project and Organization

-

Before you start writing your proposal:

-
    -
  • Carefully read the project ideas listed by the organization.
    • -
  • Research past projects and contributions to understand what has been done.
    • -
  • Join Vife's Matrix GSOC channel.
    • -
  • Engage with the community and introduce yourself.
    • -
  • Reach out to mentors and admins for guidance.
    • -
  • Complete any warm-up tasks suggested by the organization.
    • -
- -

2. Structure of a Strong Proposal

-

A well-structured proposal is key to acceptance. Below is a recommended outline:

- -

Title and Personal Details

-
    -
  • Project title
    • -
  • Your full name, email, GitHub or other relevant profiles
    • -
  • Organization and project name
    • -
- -

Synopsis

-
    -
  • A short summary of the project and your planned contributions.
    • -
  • Clearly define the problem and its significance.
    • -
- -

Benefits to the Community

-
    -
  • Explain how your project benefits the open-source community and the organization.
    • -
  • Mention how it aligns with the organization's goals.
    • -
- -

Deliverables

-
    -
  • List expected deliverables with clear objectives.
    • -
  • Define project milestones with estimated completion dates.
    • -
  • Specify key technical and implementation details.
    • -
- -

Technical Details

-
    -
  • Provide a high-level overview of how you plan to implement the project.
    • -
  • List the technologies, frameworks, and tools you will use.
    • -
  • Reference existing repositories, APIs, or dependencies.
    • -
- -

Timeline

-
    -
  • Create a detailed week-by-week or phase-wise breakdown of your work.
    • -
  • Include buffer time for potential delays.
    • -
- -

Expected Outcomes

-
    -
  • Describe the final expected results, including potential extensions.
    • -
  • Discuss how the project can be maintained beyond the program period.
    • -
- -

Resources & Dependencies

-
    -
  • List any resources (software, datasets, APIs) needed for the project.
    • -
  • Mention possible blockers and how you plan to overcome them.
    • -
- -

Personal Background

-
    -
  • Summarize your education, work, and open-source experience.
    • -
  • Highlight relevant projects or contributions.
    • -
  • Link your portfolio, GitHub, blog, or any relevant work.
    • -
- -

Community Engagement

-
    -
  • Describe how you plan to communicate progress (weekly reports, blog posts, etc.).
    • -
  • Mention how you will seek feedback and collaborate with the community.
    • -
- -

Why You?

-
    -
  • Explain why you are the best candidate for the project.
    • -
  • Highlight unique skills and experiences that make you a good fit.
    • -
- -

3. Best Practices for Writing a Winning Proposal

-
    -
  • Be clear and concise: Avoid vague descriptions; be specific about deliverables and timelines.
    • -
  • Show feasibility: Ensure your proposal is realistic and can be completed within the timeframe.
    • -
  • Engage with the community: Active participation can strengthen your proposal.
    • -
  • Get feedback: Share your draft with mentors and peers for review.
    • -
  • Follow the organization’s guidelines: Each organization may have specific requirements—adhere to them strictly.
    • -
  • Proofread: A well-written, error-free proposal creates a great impression.
    • -
- -

4. Contacting Mentors and Admins

-
    -
  • Reach out via the Matrix channel.
    • -
  • Ask questions and clarify doubts about the project.
    • -
  • Request feedback on your ideas before finalizing the proposal.
    • -
- -

5. Preparing with Warm-Up Tasks

-
    -
  • Warm-up tasks help demonstrate your commitment and technical abilities.
    • -
  • Share your solutions and discuss them with mentors for feedback.
    • -
- -

Final Submission Tips

-
    -
  • Start drafting early and iterate based on feedback.
    • -
  • Double-check the submission deadline and format requirements.
    • -
  • Submit before the deadline to avoid last-minute issues.
    • -
- -

Additional Resources

- - -

GOOD LUCK!

-
-
\ No newline at end of file +
+

Contributor's Guide: Writing a Proposal

+

Understand the Organization

+

+ Virtual Research Network Edirom (ViFE) is an association of current and former employees of the Detmold/Paderborn Department of Musicology who are involved in various projects dealing with the application of digital methods in musicology. The common goal is to promote digital work in the field of musicological research, in particular digital text and music editions. ViFE organizes the annual Edirom Summer School. + + The network is named after the DFG project for the development of tools for digital forms of scholarly-critical music editions (2006-2012), which became known as “Edirom” and formed the starting point for a series of other digital projects. + + The focus of the network's national and international work is on the conception of digital editions and their forms of publication, the application and further development of relevant standards (TEI, MEI) and tools, questions of data modelling and project organization, the promotion of communication between digitally working projects and institutions and the transfer of relevant knowledge and skills. The network partners are working together to develop skills in these areas in order to be available as contacts for the new digital community. +

+

Understand the Project ideas

+

Before you start writing your proposal:

+ +

Additional Resources

+ + +

GOOD LUCK!

+
+ +