Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Getting InvolvedGetting Involved
Previous
 
Next
New Post
4/30/2008 10:26 AM
 

I am interested in getting involved with the overall DNN project.  There are a few minor bugs I would like to log and a few bug fixes I could submit.  How do I gain read/write access to Gemini to log the defects?

How does one get started ghecking-out / checking-in code?

I'm sure there is a reference document out there, I just havn't seen it yet.

Thanks for your guidance.

 
New Post
4/30/2008 12:00 PM
 

For minor bugs and bug fixes, the typical route would be to create an account at our Gemini site (http://support.dotnetnuke.com/Main.aspx) and then log the issues in the DNN Core Framework Public project.

Hope this helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
4/30/2008 12:08 PM
 

Hi Bryan,

You'll need to use the Gemini work-item tracking system located at support.dotnetnuke.com to log work items.  Once you create an account, you'll have access to the public DNN project areas.  The workflow system used here involves a DNN team member (usually Alex) validating the issue, after which it is moved to the "main" project for further review by the core team.  In my experience, I have found them very responsive to issues submitted in this manner, with the likelihood of incorporation being greatly increased with detailed code corrections.

This is the extent of public interaction with the DNN source.  Non-core members are limited to posting their suggested code modifications within the work item for the core team to review.  As far as I am aware, there is no publicly-accessible checkout/checkin process available.

I'll leave it to those with more authority to suggest other ways in which a person might become more involved with the DNN project.

Brandon


Brandon Haynes
BrandonHaynes.org
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Getting InvolvedGetting Involved


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out