• Home
• org.apache.wayang
• wayang-docs
• 0.6.0
• source code
• 3a52145c998abba3804b3e632b56d56060649b4cfc756430c90a7a72862c06

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

.jekyll-cache.Jekyll.Cache.Jekyll--Converters--Markdown.59.3a52145c998abba3804b3e632b56d56060649b4cfc756430c90a7a72862c06 Maven / Gradle / Ivy

I"?
Choosing What to Contribute

Wayang is a great project but currently we are searching for having more hand on the code. Review can take hours or days of committer time. Everyone benefits if contributors focus on changes that are useful, clear, easy to evaluate, and already pass basic checks.

Sometimes, a contributor will already have a particular new change or bug in mind. If seeking ideas, consult the list of starter tasks in Jira Issues, or ask the email list@dev.

Before proceeding, contributors should evaluate if the proposed change is likely to be relevant, new and actionable:


  

    
Is it clear that code must change? Proposing a Jira Issues and pull request is appropriate only when a clear problem or change has been identified. If simply having trouble using Wayang, use the email list@dev  first, rather than consider filing a Jira Issues or proposing a change.
  
  
Search on [email protected] for related discussions. Often, the problem has been discussed before, with a resolution that doesn’t require a code change, or recording what kinds of changes will not be accepted as a resolution.
  

    
Search Jira Issues for existing issues.
  
  
Type [search terms] at the search box. If a logically similar issue already exists, then contribute to the discussion on the existingJira Issues and pull request first, instead of creating a new one.
  
Is the scope of the change matched to the contributor’s level of experience? Anyone is qualified to suggest a typo fix, but refactoring core scheduling logic requires much more understanding of Wayang. Some changes require building up experience first.



It’s worth reemphasizing that changes to the core of Wayang, or to highly complex and important modules, are more difficult to make correctly. They will be subjected to more scrutiny, and held to a higher standard of review than changes to less critical code. As result of this, is important to be pacient in the coordination with Wayang Community to be sure that everything can works well after the change.


:ET