Skip to content
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.

Sign up for GitHub

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

Jump to bottom

How to handle old issues? #589

Closed
304NotModified opened this issue Feb 19, 2015 · 19 comments
Closed

How to handle old issues? #589

304NotModified opened this issue Feb 19, 2015 · 19 comments
Labels
discussion

Comments

@304NotModified
Copy link
Member

There a lot of issues on GitHub. (+25 of 2012). I don't like open issues, and especially I dislike open bug reports.

What should be do with those old bug reports? Maybe we have to make them top priority?
@304NotModified 304NotModified changed the title Old issues How to handle old issues? Feb 19, 2015
@ghost
Copy link

ghost commented Feb 19, 2015 via email

@Ninja4Code
Copy link

I'm interested in contributing to the project, either in coding or documentation. What's the best way to get my feet wet? I am a C# developer. I've been using NLog for several years.

Charles

@osintra
Copy link

osintra commented Mar 30, 2015

Same situation here
On Mar 29, 2015 10:58 PM, "Charles Owen" notifications@github.com wrote:

I'm interested in contributing to the project, either in coding or
documentation. What's the best way to get my feet wet. I am a C# developer.
I've been using NLog for several years.

Charles

—
Reply to this email directly or view it on GitHub
#589 (comment).

@304NotModified
Copy link
Member Author

Great!

I will post some stuff where you could get started with later this day.

@304NotModified
Copy link
Member Author

Hi @Ninja4Code and @osintra

Thanks for your interest in contributing to NLog. Contributions are really appreciated!

The following GitHub issues are nice to start with:

Too bad you can't assign yourself. You need to be contributor for that. At the moment only @Xharze can assign you as contributor, but I guess he is still on vacation.

@Ninja4Code
Copy link

Thanks for responding...

I'm assuming I need to check out the code and build it locally? Is there a set of instructions for that with coding conventions, etc? Could I get the code base working in Visual Studio, etc?

Thanks
Chuck

Date: Mon, 30 Mar 2015 08:13:36 -0700
From: notifications@github.com
To: NLog@noreply.github.com
CC: owen.charlesr@hotmail.com
Subject: Re: [NLog] How to handle old issues? (#589)

Hi @Ninja4Code and @osintra

Thanks for your interest in contributing to NLog. Contributions are really appreciated!

The following GitHub issues are nice to start with:

If you like to work with Mono: #648

This issue would be great if it get fixed (and unit tested): #273

If you like to create an layout renderer (small task): #86

If you good in writing English or just like writing English: #595, #520

If you like to work with Sandcastle Help File Builder (SHFB): #655

—
Reply to this email directly or view it on GitHub.

@304NotModified
Copy link
Member Author

The best way to get started (flow)

  1. Fork the NLog repos. (eg. Ninja4Code/NLog)
  2. Create a new branch in you current repos (Ninja4Code/NLog) from the 'master' branch.
  3. 'Check out' the code with Git or GitHub for Windows
  4. push commits and create a Pull Request (PR) to NLog

Note: I use GitHub for Windows and develop locally with Visual Studio 2013.

If you haven't seen CONTRIBUTING.md yet, it could be useful the read it :)

About the code guidelines, there aren't code lines yet. I think this should be fixed this year.

@304NotModified
Copy link
Member Author

@Ninja4Code if you need some more info, feel free to ask.

Maybe good to know, are you a Windows user? Are you experienced with Git and Github? (no problem if not)

@Ninja4Code
Copy link

Julian,

Thanks for the info. I'll give you an update in 24 hours.

Chuck

Date: Mon, 30 Mar 2015 08:22:14 -0700
From: notifications@github.com
To: NLog@noreply.github.com
CC: owen.charlesr@hotmail.com
Subject: Re: [NLog] How to handle old issues? (#589)

The best way to get started (flow)

Fork the NLog repos. (eg. Ninja4Code/NLog)
Create a new branch in you current repos (Ninja4Code/NLog) from the 'master' branch.
'Check out' the code with Git or GitHub for Windows

—
Reply to this email directly or view it on GitHub.

@Ninja4Code
Copy link

I have developed both on Windows and Linux environments, but mostly Windows. My development has spanned most of the .NET Projects (MVC, SOA, WPF, etc). Yes, I have just installed the Windows GIT Client.

Thanks,
Chuck

Date: Mon, 30 Mar 2015 08:29:02 -0700
From: notifications@github.com
To: NLog@noreply.github.com
CC: owen.charlesr@hotmail.com
Subject: Re: [NLog] How to handle old issues? (#589)

@Ninja4Code if you need some more info, feel free to ask.

Maybe good to know, are you a Windows user? Are you experienced with Git and Github? (no problem if not)

—
Reply to this email directly or view it on GitHub.

@Ninja4Code
Copy link

I was able to fork and clone the repository successfully.

Charles

Date: Mon, 30 Mar 2015 08:29:02 -0700
From: notifications@github.com
To: NLog@noreply.github.com
CC: owen.charlesr@hotmail.com
Subject: Re: [NLog] How to handle old issues? (#589)

@Ninja4Code if you need some more info, feel free to ask.

Maybe good to know, are you a Windows user? Are you experienced with Git and Github? (no problem if not)

—
Reply to this email directly or view it on GitHub.

@304NotModified
Copy link
Member Author

Any success with the code @Ninja4Code?

@Ninja4Code
Copy link

Ninja4Code commented Apr 16, 2015 via email

@304NotModified
Copy link
Member Author

Closing this discussion ("How to handle old issues?"). If you need some help @Ninja4Code , feel free to post in the referenced issues or contact me at Gitter (https://gitter.im/NLog/NLog)

@Ninja4Code
Copy link

I apologize I haven't contributed yet but I definitely intend to in the near future. I'll contact you again when I get involved in the code. I had to spend a lot of time finishing up my schoolwork for the semester.

Charles

Date: Thu, 14 May 2015 02:40:40 -0700
From: notifications@github.com
To: NLog@noreply.github.com
CC: owen.charlesr@hotmail.com
Subject: Re: [NLog] How to handle old issues? (#589)

Closing this discussion ("How to handle old issues?"). If you need some help @Ninja4Code , feel free to post in the referenced issues or contact me at Gitter (https://gitter.im/NLog/NLog)

—
Reply to this email directly or view it on GitHub.

@304NotModified
Copy link
Member Author

@Ninja4Code No problem. Some things have to be done.

We will appreciate any contributions like code, (unit) tests or other feedback. On the readme I have added the Github issues if you like to start with something.

@Ninja4Code
Copy link

I know I didn’t contribute last time, but I’m making a humble request to try again. What’s the best way for me to start? Should I open the code in Visual Studio 2013 or 2015? Again, my apologies for inactivity in the past.

Charles Owen

Sent from Windows Mail

From: Julian Verdurmen
Sent: ‎Wednesday‎, ‎April‎ ‎15‎, ‎2015 ‎4‎:‎02‎ ‎PM
To: NLogNLog
Cc: Charles Owen

Any success with the code @Ninja4Code?

—
Reply to this email directly or view it on GitHub.

@304NotModified
Copy link
Member Author

hey! NP! We are aware helping takes some free time, and sometimes there is less then planned.

We still try to keep the code VS2013 compatible, but we will move soon to VS2015 (guess after 4.4)

There is some info on contributing over here: https://github.com/NLog/NLog#contributing

I think the following would be nice to do IMO:

@Ninja4Code
Copy link

Thanks, I will try to work on the issues at the bottom

Charles

Sent from Windows Mail

From: Julian Verdurmen
Sent: ‎Saturday‎, ‎August‎ ‎13‎, ‎2016 ‎6‎:‎52‎ ‎PM
To: NLogNLog
Cc: Charles Owen, Mention

hey! NP! We are aware helping takes some free time, and sometimes there is less then planned.

We still try to keep the code VS2013 compatible, but we will move soon to VS2015 (guess after 4.4)

There is some info on contributing over here: https://github.com/NLog/NLog#contributing

I think the following would be nice to do IMO:
#1436
#1406
#1181

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@osintra @304NotModified @Ninja4Code