acezen commented on issue #495:
URL: 
https://github.com/apache/incubator-graphar/issues/495#issuecomment-2129255745

   > > > Firstly, thank you for asking! Here are my suggestions:
   > > > 
   > > > 1. Tips for development containers: Using development containers to 
assist rookies is a great idea. However, rookies might not know how to use 
them. Providing tips or recommendations would be helpful. For example, in the 
(graphscope) project's developer guide, I learned how to use the VSCode Remote 
plugin with development containers. Posting links to related tutorials could 
also be beneficial.
   > > > 2. Local testing guidance: I prefer to test locally before submitting 
a Pull Request (PR) to respect the community managers' time. If I can identify 
and fix issues through local testing, it saves them trouble. However, I haven't 
found a tutorial for local testing.
   > > > 3. Different developer guides: I suggest having separate developer 
guides for rookies and veterans. This way, rookies won't be confused by too 
concise instructions, and veterans won't be overwhelmed by too much information.
   > > > 
   > > > These are my current suggestions. If I have more in the future, I'd be 
happy to share again.
   > > > Also, I'd like to offer my help in creating a developer guide for 
rookies. As a rookie, I understand their needs best.
   > > 
   > > 
   > > Thanks for the suggestions. It would be helpful if you can help to draft 
a developer guide for new contributor. You can start from C++ library.
   > 
   > Can I open a PR to sync this with the community?
   
   Yes, feel free to open a sub-issue and PR for the work


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to