-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Communicating and reporting project metrics #6
Comments
Hello sir , Thanks and regards |
The best application for this project would include links to similar documentation you have written in the past, e.g., monthly/annual reports, presentation of usage stats, roadmaps, etc. The best application would also include a review of the documentation we have already (links in project description) and specific recommendations for improvements. Please be aware: this is a technical writing project, not a code writing project. |
Hey @AlexanderPico I was just going through the project and the provided links.
I went to the links Usage Stats and Roadmap and we can possibly have different sections to show how the project helps different parties in their relevant space. Please take a look at the following for my sample work
|
@sidkapoor97 Very nice. The approach looks sound to me. Please draft an application fleshing out each point in more detail. Feel free to use real usage data (or fake data that we haven't collected yet) in preparing mockups and examples. I'd also recommend proposing two phases: one that focuses on an incremental improvement to what we have already (to guarantee deliverable progress) and a subsequent phase that is more involved (i.e., would be nice to have). If you prepare your draft as a Google doc, you could then share access with me and other potential mentors. Email directly to include links to your draft, etc. |
Sure, thanks for the feedback I will start working on it right away. |
@sidkapoor97 Also, given your js skills, you might also want to consider Project #3. According to the rules, you are allowed to submit a maximum of 3 applications. |
Hello, |
@madi1234-oss Welcome. These are all open source projects that you can contribute to and reuse at any time. The Google Summer of Code (GSoC) program is for software engineers. That's already begun for 2020. The Google Season of Docs (GSoD) program is for technical writers. |
Dear Alexander Pico,
I want to use GSoD platform as a technical writer, i have experience of writing as my two research articles have been published on international scientific Journals. In addition, I have completed my Bachelors and M.Phil. with participating in so many assignments and poster presentations.
Regards
Sent from Yahoo Mail on Android
On Tue, Jun 9, 2020 at 2:27 AM, Alexander Pico<[email protected]> wrote:
@madi1234-oss Welcome. These are all open source projects that you can contribute to and reuse at any time. The Google Summer of Code (GSoC) program is for software engineers. That's already begun for 2020. The Google Season of Docs (GSoD) program is for technical writers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Great. Timeline and instructions for GSoD are here: https://developers.google.com/season-of-docs/docs/timeline |
@AlexanderPico I have Submitted the proposal. Please have a look at it so that I can fulfill the missing part. |
Background
As an open source project we have regular reporting duties to diverse stakeholders, including government funding agencies and industry funders. We also feel a strong responsibilty to our communities developers, users and potential users. Currently, we have website pages that list compiled stats and metrics, as well as a roadmap.
Goal
With your help, we'd like to clarify the goals of reporting, identify which metrics are most important, and work on communicating them through diverse media and language, e.g., narratives vs graphs vs infoviz docs, etc.
By the end of GSoD, we like to have:
Technical Skills
Link
Potential Mentors
Alex Pico
Contact
Alex Pico
The text was updated successfully, but these errors were encountered: