Closed BendixSpring closed 8 years ago
romichg
commented
11 years ago This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris notifications@github.comwrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12 .
BendixSpring
commented
11 years ago Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris <notifications@github.com mailto:notifications@github.com >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12 .
— Reply to this email directly or view it on GitHub https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309 . https://github.com/notifications/beacon/5F2_eRmNmMOSmJQY77zQB9aGAdMzMLMXyLF_3evQNqwQJ1ydxqb0o-XgeYKai-dX.gif
romichg
commented
11 years ago You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris <notifications@github.com<mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309> . < https://github.com/notifications/beacon/5F2_eRmNmMOSmJQY77zQB9aGAdMzMLMXyLF_3evQNqwQJ1ydxqb0o-XgeYKai-dX.gif>
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061 .
DinisCruz
commented
11 years ago And questions like Danny's should be answered with a link to TM4TM :)
Dinis Cruz
On 19 Apr 2013, at 05:42, Roman Garber notifications@github.com wrote:
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris <notifications@github.com<mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309> . < https://github.com/notifications/beacon/5F2_eRmNmMOSmJQY77zQB9aGAdMzMLMXyLF_3evQNqwQJ1ydxqb0o-XgeYKai-dX.gif>
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061 .
— Reply to this email directly or view it on GitHub.
BendixSpring
commented
11 years ago I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris <notifications@github.com<mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309> . < https://github.com/notifications/beacon/5F2_eRmNmMOSmJQY77zQB9aGAdMzMLMXyLF_3evQNqwQJ1ydxqb0o-XgeYKai-dX.gif>
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061 .
— Reply to this email directly or view it on GitHub https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535 .
DinisCruz
commented
11 years ago almost :)
TMContent/Lib_Docs should be for issues related with the docs.teammentor.netsite
TMContent/Lib_All is where you can put general content issues
Dinis
Dinis Cruz
Blog: http://diniscruz.blogspot.com Twitter: http://twitter.com/DinisCruz Web: http://www.owasp.org/index.php/O2
On 19 April 2013 19:41, Danny Harris notifications@github.com wrote:
I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris <notifications@github.com <mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309> . <
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061> .
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535> .
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16674486 .
romichg
commented
11 years ago And yes this should be in TM4TM.. see FAQ item #14 and 15 in tm4tm.teammentor.net/article/00000000-0000-0000-0000-0000002f52ba (Dinis could you pull content from github for this to be there ;))
On Sat, Apr 20, 2013 at 12:15 AM, Dinis Cruz notifications@github.comwrote:
almost :)
TMContent/Lib_Docs should be for issues related with the docs.teammentor.netsite
TMContent/Lib_All is where you can put general content issues
Dinis
Dinis Cruz
Blog: http://diniscruz.blogspot.com Twitter: http://twitter.com/DinisCruz Web: http://www.owasp.org/index.php/O2
On 19 April 2013 19:41, Danny Harris notifications@github.com wrote:
I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris < notifications@github.com <mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309>
. <
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061> .
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535> .
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16674486> .
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16675129 .
DinisCruz
commented
11 years ago Humm, I don't see item #14 and #15 in there (using an IPad)
Also what do you mean by 'pull content from GitHub'?
Dinis Cruz
On 20 Apr 2013, at 14:46, Roman Garber notifications@github.com wrote:
And yes this should be in TM4TM.. see FAQ item #14 and 15 in tm4tm.teammentor.net/article/00000000-0000-0000-0000-0000002f52ba (Dinis could you pull content from github for this to be there ;))
On Sat, Apr 20, 2013 at 12:15 AM, Dinis Cruz notifications@github.comwrote:
almost :)
TMContent/Lib_Docs should be for issues related with the docs.teammentor.netsite
TMContent/Lib_All is where you can put general content issues
Dinis
Dinis Cruz
Blog: http://diniscruz.blogspot.com Twitter: http://twitter.com/DinisCruz Web: http://www.owasp.org/index.php/O2
On 19 April 2013 19:41, Danny Harris notifications@github.com wrote:
I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris < notifications@github.com <mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309>
. <
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061> .
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535> .
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16674486> .
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16675129> .
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16704261 .
romichg
commented
11 years ago Meaning that I updated the content in github library but I dont have admin on tm4tm so I cant pull it from github:) On Apr 20, 2013 11:19 PM, "Dinis Cruz" notifications@github.com wrote:
Humm, I don't see item #14 and #15 in there (using an IPad)
Also what do you mean by 'pull content from GitHub'?
Dinis Cruz
On 20 Apr 2013, at 14:46, Roman Garber notifications@github.com wrote:
And yes this should be in TM4TM.. see FAQ item #14 and 15 in tm4tm.teammentor.net/article/00000000-0000-0000-0000-0000002f52ba (Dinis could you pull content from github for this to be there ;))
On Sat, Apr 20, 2013 at 12:15 AM, Dinis Cruz notifications@github.comwrote:
almost :)
TMContent/Lib_Docs should be for issues related with the docs.teammentor.netsite
TMContent/Lib_All is where you can put general content issues
Dinis
Dinis Cruz
Blog: http://diniscruz.blogspot.com Twitter: http://twitter.com/DinisCruz Web: http://www.owasp.org/index.php/O2
On 19 April 2013 19:41, Danny Harris notifications@github.com wrote:
I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris < notifications@github.com <mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub <
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309>
. <
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061>
.
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16674486> .
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16675129> .
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16704261> .
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16708205 .
DinisCruz
commented
11 years ago You can trigger a pull from the live TM4TM by making a change there
(Btw I just made you an admin on tm4tm)
Dinis Cruz
On 20 Apr 2013, at 19:23, Roman Garber notifications@github.com wrote:
Meaning that I updated the content in github library but I dont have admin on tm4tm so I cant pull it from github:) On Apr 20, 2013 11:19 PM, "Dinis Cruz" notifications@github.com wrote:
Humm, I don't see item #14 and #15 in there (using an IPad)
Also what do you mean by 'pull content from GitHub'?
Dinis Cruz
On 20 Apr 2013, at 14:46, Roman Garber notifications@github.com wrote:
And yes this should be in TM4TM.. see FAQ item #14 and 15 in tm4tm.teammentor.net/article/00000000-0000-0000-0000-0000002f52ba (Dinis could you pull content from github for this to be there ;))
On Sat, Apr 20, 2013 at 12:15 AM, Dinis Cruz notifications@github.comwrote:
almost :)
TMContent/Lib_Docs should be for issues related with the docs.teammentor.netsite
TMContent/Lib_All is where you can put general content issues
Dinis
Dinis Cruz
Blog: http://diniscruz.blogspot.com Twitter: http://twitter.com/DinisCruz Web: http://www.owasp.org/index.php/O2
On 19 April 2013 19:41, Danny Harris notifications@github.com wrote:
I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris < notifications@github.com <mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub <
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309>
. <
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061>
.
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16674486> .
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16675129> .
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16704261> .
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16708205 .
— Reply to this email directly or view it on GitHub.
DinisCruz
commented
11 years ago my last comment is not 100% correct. I just did a 'reload cache' at tm4tm and the new content is there (the save will not reload the cache)
Dinis Cruz
On 20 Apr 2013, at 19:23, Roman Garber notifications@github.com wrote:
Meaning that I updated the content in github library but I dont have admin on tm4tm so I cant pull it from github:) On Apr 20, 2013 11:19 PM, "Dinis Cruz" notifications@github.com wrote:
Humm, I don't see item #14 and #15 in there (using an IPad)
Also what do you mean by 'pull content from GitHub'?
Dinis Cruz
On 20 Apr 2013, at 14:46, Roman Garber notifications@github.com wrote:
And yes this should be in TM4TM.. see FAQ item #14 and 15 in tm4tm.teammentor.net/article/00000000-0000-0000-0000-0000002f52ba (Dinis could you pull content from github for this to be there ;))
On Sat, Apr 20, 2013 at 12:15 AM, Dinis Cruz notifications@github.comwrote:
almost :)
TMContent/Lib_Docs should be for issues related with the docs.teammentor.netsite
TMContent/Lib_All is where you can put general content issues
Dinis
Dinis Cruz
Blog: http://diniscruz.blogspot.com Twitter: http://twitter.com/DinisCruz Web: http://www.owasp.org/index.php/O2
On 19 April 2013 19:41, Danny Harris notifications@github.com wrote:
I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris < notifications@github.com <mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub <
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309>
. <
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061>
.
— Reply to this email directly or view it on GitHub < https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16674486> .
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16675129> .
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16704261> .
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16708205 .
— Reply to this email directly or view it on GitHub.
romichg
commented
11 years ago FAQ now has items 14 and 15. I didn't do anything btw, so the question is, how often will the pull happen? Thanks for making me admin btw.
On Sun, Apr 21, 2013 at 4:13 PM, Dinis Cruz notifications@github.comwrote:
my last comment is not 100% correct. I just did a 'reload cache' at tm4tm and the new content is there (the save will not reload the cache)
Dinis Cruz
On 20 Apr 2013, at 19:23, Roman Garber notifications@github.com wrote:
Meaning that I updated the content in github library but I dont have admin on tm4tm so I cant pull it from github:) On Apr 20, 2013 11:19 PM, "Dinis Cruz" notifications@github.com wrote:
Humm, I don't see item #14 and #15 in there (using an IPad)
Also what do you mean by 'pull content from GitHub'?
Dinis Cruz
On 20 Apr 2013, at 14:46, Roman Garber notifications@github.com wrote:
And yes this should be in TM4TM.. see FAQ item #14 and 15 in tm4tm.teammentor.net/article/00000000-0000-0000-0000-0000002f52ba (Dinis could you pull content from github for this to be there ;))
On Sat, Apr 20, 2013 at 12:15 AM, Dinis Cruz notifications@github.comwrote:
almost :)
TMContent/Lib_Docs should be for issues related with the docs.teammentor.netsite
TMContent/Lib_All is where you can put general content issues
Dinis
Dinis Cruz
Blog: http://diniscruz.blogspot.com Twitter: http://twitter.com/DinisCruz Web: http://www.owasp.org/index.php/O2
On 19 April 2013 19:41, Danny Harris notifications@github.com wrote:
I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com
wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris < notifications@github.com <mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub <
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309>
. <
— Reply to this email directly or view it on GitHub<
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061>
.
— Reply to this email directly or view it on GitHub <
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535>
.
— Reply to this email directly or view it on GitHub<
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16674486>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16675129>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16704261>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16708205> .
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16719624 .
DinisCruz
commented
11 years ago I did the cache reload
Dinis Cruz
On 21 Apr 2013, at 17:42, Roman Garber notifications@github.com wrote:
FAQ now has items 14 and 15. I didn't do anything btw, so the question is, how often will the pull happen? Thanks for making me admin btw.
On Sun, Apr 21, 2013 at 4:13 PM, Dinis Cruz notifications@github.comwrote:
my last comment is not 100% correct. I just did a 'reload cache' at tm4tm and the new content is there (the save will not reload the cache)
Dinis Cruz
On 20 Apr 2013, at 19:23, Roman Garber notifications@github.com wrote:
Meaning that I updated the content in github library but I dont have admin on tm4tm so I cant pull it from github:) On Apr 20, 2013 11:19 PM, "Dinis Cruz" notifications@github.com wrote:
Humm, I don't see item #14 and #15 in there (using an IPad)
Also what do you mean by 'pull content from GitHub'?
Dinis Cruz
On 20 Apr 2013, at 14:46, Roman Garber notifications@github.com wrote:
And yes this should be in TM4TM.. see FAQ item #14 and 15 in tm4tm.teammentor.net/article/00000000-0000-0000-0000-0000002f52ba (Dinis could you pull content from github for this to be there ;))
On Sat, Apr 20, 2013 at 12:15 AM, Dinis Cruz notifications@github.comwrote:
almost :)
TMContent/Lib_Docs should be for issues related with the docs.teammentor.netsite
TMContent/Lib_All is where you can put general content issues
Dinis
Dinis Cruz
Blog: http://diniscruz.blogspot.com Twitter: http://twitter.com/DinisCruz Web: http://www.owasp.org/index.php/O2
On 19 April 2013 19:41, Danny Harris notifications@github.com wrote:
I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com
wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris < notifications@github.com <mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub <
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309>
. <
— Reply to this email directly or view it on GitHub<
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061>
.
— Reply to this email directly or view it on GitHub <
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535>
.
— Reply to this email directly or view it on GitHub<
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16674486>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16675129>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16704261>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16708205> .
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16719624> .
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16732161 .
DinisCruz
commented
11 years ago The pull will happen on:
Apart from the cache reload one, the others will not update the cache
Dinis Cruz
On 21 Apr 2013, at 17:42, Roman Garber notifications@github.com wrote:
FAQ now has items 14 and 15. I didn't do anything btw, so the question is, how often will the pull happen? Thanks for making me admin btw.
On Sun, Apr 21, 2013 at 4:13 PM, Dinis Cruz notifications@github.comwrote:
my last comment is not 100% correct. I just did a 'reload cache' at tm4tm and the new content is there (the save will not reload the cache)
Dinis Cruz
On 20 Apr 2013, at 19:23, Roman Garber notifications@github.com wrote:
Meaning that I updated the content in github library but I dont have admin on tm4tm so I cant pull it from github:) On Apr 20, 2013 11:19 PM, "Dinis Cruz" notifications@github.com wrote:
Humm, I don't see item #14 and #15 in there (using an IPad)
Also what do you mean by 'pull content from GitHub'?
Dinis Cruz
On 20 Apr 2013, at 14:46, Roman Garber notifications@github.com wrote:
And yes this should be in TM4TM.. see FAQ item #14 and 15 in tm4tm.teammentor.net/article/00000000-0000-0000-0000-0000002f52ba (Dinis could you pull content from github for this to be there ;))
On Sat, Apr 20, 2013 at 12:15 AM, Dinis Cruz notifications@github.comwrote:
almost :)
TMContent/Lib_Docs should be for issues related with the docs.teammentor.netsite
TMContent/Lib_All is where you can put general content issues
Dinis
Dinis Cruz
Blog: http://diniscruz.blogspot.com Twitter: http://twitter.com/DinisCruz Web: http://www.owasp.org/index.php/O2
On 19 April 2013 19:41, Danny Harris notifications@github.com wrote:
I’ve discovered https://github.com/TMContent/
So the Lib_XXX are content libraries. If I find a specific issue (typo, mistake, etc) with one of those libraries or have a content suggestion, just open an Issue there. Correct?
Then TMContent/Lib_Docs is used for general content issues?
If there is a bug or feature request or functionality suggestion, then general issues go to TeamMentor/Master. Correct?
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Friday, April 19, 2013 12:42 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
You are correct, other than content issues should go into their respective library repositories. For example Java content issues should go into TMContent/Lib_Java. Content related issues that are not library specific or span multiple libraries should go to Lib_All. Lib_Docs is a library for TM documentation. The library you see on docs.teammentor.netnet On Apr 19, 2013 9:11 AM, "Danny Harris" notifications@github.com
wrote:
Roman:
I must not understand what goes where.
I was under the impression this is the master log for all things !content: https://github.com/TeamMentor/Master/issues?state=open
And I was under the impression that this is for content-issues: https://github.com/TMContent/Lib_Docs/issues
That’s what I know about. Are there other places to post comments? Lemme know and give me the criteria, and I will do it.
Thanks,
Danny
From: Roman Garber [mailto:notifications@github.com] Sent: Thursday, April 18, 2013 10:51 PM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] CWE Library should be renamed to CWE/SANS Top 25 (#12)
This is good, but shouldn't this go to the CWE library repo :)?
On Thu, Apr 18, 2013 at 8:33 PM, Danny Harris < notifications@github.com <mailto: notifications@github.com> >wrote:
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12> .
— Reply to this email directly or view it on GitHub <
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16627309>
. <
— Reply to this email directly or view it on GitHub<
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16632061>
.
— Reply to this email directly or view it on GitHub <
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16635535>
.
— Reply to this email directly or view it on GitHub<
https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16674486>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16675129>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16704261>
.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16708205> .
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub< https://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16719624> .
— Reply to this email directly or view it on GitHubhttps://github.com/TMContent/Lib_Docs/issues/12#issuecomment-16732161 .
romichg
commented
8 years ago This is actually done.
The official title is something like this: 2011 CWE/SANS Top 25 Most Dangerous Software Errors (http://cwe.mitre.org/top25/)
CWE is a superset of the Top 25.
--Danny