upstream-devel Mailing List for Upstream Log Transfer System (Page 2)
Status: Alpha
Brought to you by:
mweerasinghe
Menu
▾
▴
upstream-devel — Upstream Developer List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
(11) |
Oct
(29) |
Nov
(27) |
Dec
(18) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(5) |
Feb
(11) |
Mar
(9) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Mahangu W. <ma...@gm...> - 2007-01-19 13:10:04
|
Awesome. How about Saturday evening my time (GMT + 5.30). Any time between three and nine should be fine. Not sure what time that is for you guys. On 1/19/07, Ryan Zeigler <zei...@gm...> wrote: > Hello everyone, > So I know that there have been some plans for a meeting that have cropped up > from time to time, but have never really materialized. I just wanted to throw > out there that I'm good for a meeting pretty much anytime in the next few > days except sunday. > > Ryan > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > -- I can do everything through him who gives me strength. - Philippians 4:13 (NIV) |
|
From: Ryan Z. <zei...@gm...> - 2007-01-19 13:00:50
|
Hello everyone, So I know that there have been some plans for a meeting that have cropped up from time to time, but have never really materialized. I just wanted to throw out there that I'm good for a meeting pretty much anytime in the next few days except sunday. Ryan |
|
From: Mahangu W. <ma...@gm...> - 2007-01-12 13:08:50
|
Hi Karl, This has now been implemented in Upstream-base. For example, you can now run - lsmod | ./upstream foo foo and it will send the output of lsmod to the default pastebin server. You can use the --pastebin flag to specify an output server as well. Grab a copy of trunk/ and check it out. Let us know if you run in to any hitches. Now all that remains to be done is to write the module for $BTS. :-) Regards, Mahangu On 1/10/07, Karl Goetz <kam...@in...> wrote: > Hi all, > I was asked to forward this idea to this list after privately emailing > it to someone. I've edited it a little, but its the same idea. > > ** > > Because of Upstream-devs modular design, where the output goes (ie which > target host) is arbitrary. > I think if a std in module could be made for Upstream-dev it could be > used just as easily for sending patches to BTS's as it is to send output > to pastebins. > > I envisage something like this (i just make up the switch). > > diff badcode.py fixedcode.py |upstream --bts=bugs.gnewsense.org - > > that line would take the input (for us a diff), and output it to the > server specified (bugs.gnewsense.org). > > the BTS, as far as the upstream codebase is concerned, is another module > (aka a pastebin) read from stdin is just another source of input. > > I thought it was worth sharing the idea, as it might be practical, > depending on how BTS's work. > > Even if it cant be used to send patches directly to a bts (lack of > support for such things), it would be a great way to put a diff strait > up to a pastebin. > > ** > > Hope It makes sense, > kk > > -- > Karl Goetz > User of gNewSense: Free as in Freedom - http://www.gnewsense.org > Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam > Debian, The Universal Operating System - http://www.debian.org > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > -- I can do everything through him who gives me strength. - Philippians 4:13 (NIV) |
|
From: Karl G. <kam...@in...> - 2007-01-10 00:40:31
|
Hi all, I was asked to forward this idea to this list after privately emailing it to someone. I've edited it a little, but its the same idea. ** Because of Upstream-devs modular design, where the output goes (ie which target host) is arbitrary. I think if a std in module could be made for Upstream-dev it could be used just as easily for sending patches to BTS's as it is to send output to pastebins. I envisage something like this (i just make up the switch). diff badcode.py fixedcode.py |upstream --bts=bugs.gnewsense.org - that line would take the input (for us a diff), and output it to the server specified (bugs.gnewsense.org). the BTS, as far as the upstream codebase is concerned, is another module (aka a pastebin) read from stdin is just another source of input. I thought it was worth sharing the idea, as it might be practical, depending on how BTS's work. Even if it cant be used to send patches directly to a bts (lack of support for such things), it would be a great way to put a diff strait up to a pastebin. ** Hope It makes sense, kk -- Karl Goetz User of gNewSense: Free as in Freedom - http://www.gnewsense.org Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam Debian, The Universal Operating System - http://www.debian.org |
|
From: Mahangu W. <ma...@gm...> - 2006-12-10 11:50:25
|
Hi Everyone, I just thought I'd point this out - http://packages.debian.org/testing/admin/upstreamdev and say well done, everyone! :-) It's been a fantastic ride so far. Upstream has come a long way from being the clunky little bash script it was just a few months ago. It's been a pleasure working with each and every one of you. Here's to Wordsworth, Blake and beyond! :-) Regards, Mahangu |
|
From: Mahangu W. <ma...@gm...> - 2006-12-08 18:59:46
|
Hi Karl, > > i agree. capital S in Software. > its had aspell run over it now, so hopefully that fixes those issues ;). > i will point out chunks of it were copied from (iirc) the wiki. It may > need spell checking as well ;) Hmmm, you can run the bits from the wiki through aspell just to be sure, but I reckon they're good. They all went through the spell checker in my head. ;-) Sorry if I came across as anal retentive regarding the spelling, but that's what they did to me during first year English. I'm majoring now, and lose sleep over things like misplaced apostrophes and mixed up tenses. :\ > its had a few things tweaked (like i tacked in the website URL at the > bottom) as well. > it would be nice if someone could look at the FIXME's as well. > kk Sure, thanks. I'll fill in the blanks tomorrow morning when I wake up. Btw something we should think about is syncing this man page with the upstream -h output. For example, I like your >upstream your-name "Your problem description" [options] better than what we have in upstream-base right now. Anyway that's only after we finalize the man page, so we'll leave it for later. :-) Thanks again for the quick response. It's greatly appreciated in a documenter, especially when other projects lag behind with their docs. Great to have you aboard, Karl! Looking forward to working with you on 0.3 and beyond. Regards, Mahangu |
|
From: Ryan Z. <zei...@gm...> - 2006-12-08 17:17:06
|
Hello all, So, currently, I believe there is a workable framework in place for the=20 altered submission module system. However, shaking out the kinks and other= =20 things requires porting at least one frontend and at least one submission=20 module to use the new framework. So, if anyone wants to break and fix,=20 checkout the advsubmit branch and go to work. Ryan |
|
From: Karl G. <kam...@in...> - 2006-12-08 15:44:11
|
Karl Goetz wrote: > Mahangu Weerasinghe wrote: > >> Looks good, Karl. Just a few changes I would make - >> >> >>> Upstream is Free software. It is released under the terms of the GNU >>> GPL 2.0 or >>> >> 'Free Software' sounds better, imho. >> >> Also a few small spelling mistakes like "meantion" and "unable to find >> / c these," but I assume you'll catch these during the qa check. Don't >> want to nitpick further right now, so will leave this to develop a bit >> before commenting on it again. Please use this same thread when >> updating the file. Thanks! >> >> >> > > i agree. capital S in Software. > its had aspell run over it now, so hopefully that fixes those issues ;). > i will point out chunks of it were copied from (iirc) the wiki. It may > need spell checking as well ;) > its had a few things tweaked (like i tacked in the website URL at the > bottom) as well. > it would be nice if someone could look at the FIXME's as well. > kk > > Now with attachment. after 2 am, what did i expect... kk -- Karl Goetz User of gNewSense: Free as in Freedom - http://www.gnewsense.org Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam Debian, The Universal Operating System - http://www.debian.org |
|
From: Karl G. <kam...@in...> - 2006-12-08 15:40:57
|
Mahangu Weerasinghe wrote: > Looks good, Karl. Just a few changes I would make - > >> Upstream is Free software. It is released under the terms of the GNU >> GPL 2.0 or > 'Free Software' sounds better, imho. > > Also a few small spelling mistakes like "meantion" and "unable to find > / c these," but I assume you'll catch these during the qa check. Don't > want to nitpick further right now, so will leave this to develop a bit > before commenting on it again. Please use this same thread when > updating the file. Thanks! > > i agree. capital S in Software. its had aspell run over it now, so hopefully that fixes those issues ;). i will point out chunks of it were copied from (iirc) the wiki. It may need spell checking as well ;) its had a few things tweaked (like i tacked in the website URL at the bottom) as well. it would be nice if someone could look at the FIXME's as well. kk -- Karl Goetz User of gNewSense: Free as in Freedom - http://www.gnewsense.org Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam Debian, The Universal Operating System - http://www.debian.org |
|
From: Mahangu W. <ma...@gm...> - 2006-12-08 15:20:33
|
Looks good, Karl. Just a few changes I would make - > Upstream is Free software. It is released under the terms of the GNU GPL 2.0 or 'Free Software' sounds better, imho. Also a few small spelling mistakes like "meantion" and "unable to find / c these," but I assume you'll catch these during the qa check. Don't want to nitpick further right now, so will leave this to develop a bit before commenting on it again. Please use this same thread when updating the file. Thanks! On 12/8/06, Karl Goetz <kam...@in...> wrote: > hi all > Now with switches! > Still, feedback welcome :) > kk > > -- > Karl Goetz > User of gNewSense: Free as in Freedom - http://www.gnewsense.org > Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam > Debian, The Universal Operating System - http://www.debian.org > > > > NAME > Upstream - A tool that allows users to send in logs and troubleshooting data to support personnel. > > SYNOPSIS > upstream yourname "Your problem description" [options] > > yourname - who the pastebin/problem is from > Your problem description - a short text identifying whats wrong (EG "apt failing to update") > options - which area to collect data for > > If no arguments are supplied, Upstream will go in to wizard mode. > > OPTIONS > > -h, --help Show this help message and exit > > One of the following is required. > --kernel Send all log modules in the kernel category. > --network Send all log modules in the network category. > --apt Send all log modules in the apt category. > --pci Send all log modules in the pci category. > --video Send all log modules in the video category. > --memory Send all log modules in the memory category. > --disk Send all log modules in the disk category. > --cpu Send all log modules in the cpu category. > --log=LOG Choose a specific a log module to use. > > Optional. > --pastebin=PASTEBIN Specify a pastebin module to use. > > DESCRIPTION > Upstream is a collection of tools that allow users to send in system specific log and troubleshooting data to support personnel. > > Upstream aims to simplify the support cycle and make it more efficient. One of the main problems that support staff face when helping people via IRC or mailing lists is getting user log files across. Often this process is time consuming, and many new users may even be unable to find / copy these logs. Occasionally, users may accidentally paste an entire log file in to an IRC channel, earning them a ban, and confusing them in the process. > > AUTHOR > This manual page was written by Karl Goetz, with the assistance of others. > Upstream is written by dev1 dev2 dev3, with contributions from others. > > COPYRIGHT > Upstream is Free software. It is released under the terms of the GNU GPL 2.0 or any later version. > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > |
|
From: Brandon W. <red...@gm...> - 2006-12-08 14:27:13
|
A reference to our site, upstreamdev.org would be nice perhaps? On 12/8/06, Karl Goetz <kam...@in...> wrote: > > Ryan Zeigler wrote: > > That looks good, the only problem is, depending on what log modules are > > shipped, thos categories may or may not be present. The actually > available > > categories are determined at runtime based on what modules are > available. > > > > > Thanks for the feedback, i have made a few changes to reflect it, along > with a few other bits and pieces. > update attached, > kk > > > Ryan > > On Friday 08 December 2006 08:04, Karl Goetz wrote: > > > >> hi all > >> Now with switches! > >> Still, feedback welcome :) > >> kk > >> > > -- > Karl Goetz > User of gNewSense: Free as in Freedom - http://www.gnewsense.org > Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam > Debian, The Universal Operating System - http://www.debian.org > > > > NAME > Upstream - A tool that allows users to send in logs and > troubleshooting data to support personnel. > > SYNOPSIS > upstream yourname "Your problem description" [options] > > yourname - who the pastebin/problem is from > Your problem description - a short text identifying whats wrong > (EG "apt failing to update"). Your problem description must be inside double > quotes. > options - which area to collect data for > > If no arguments are supplied, Upstream will go in to wizard mode. > > OPTIONS > > -h, --help Show this help message and exit > > One of the following is required. > --network Send all log modules in the network > category. > --apt Send all log modules in the apt > category. > --pci Send all log modules in the pci > category. > --memory Send all log modules in the memory > category. > --disk Send all log modules in the disk > category. > --cpu Send all log modules in the cpu > category. > --kernel Send all log modules in the kernel > category. > --video Send all log modules in the video > category. > --log=LOG Choose a specific a log module to use > Only one > --log= may be used per run of Upstream > > Optional. > --pastebin=PASTEBIN Specify a pastebin module to use. > > MODULES > These are the modules that can be loaded using --log= . Not all > these modules may be available on your system. > cpuinfo > daemon > df > dmesg > free > ifconfig > iwconfig > lsmod > lspci > netInterfaces > netstat > pci > ps > sourcelist > uname > vmstat > xorgConf > xorgLog > > > DESCRIPTION > Upstream is a collection of tools that allow users to send in system > specific log and troubleshooting data to support personnel. > If you prefer, you can aquire a frontend for Upstream, Canoe (GTK) or > Kayak (QT). > > Upstream aims to simplify the support cycle and make it more efficient. > One of the main problems that support staff face when helping people via IRC > or mailing lists is getting user log files across. Often this process is > time consuming, and many new users may even be unable to find / c these > logs. Occasionally, users may accidentally paste an entire log file in to an > IRC channel, earning them a ban, and confusing them in the process. > > AUTHOR > This manual page was written by Karl Goetz, with the assistance of > others. > FIXME Upstream is written by dev1 dev2 dev3, with contributions from > others. > > BUGS > If a module is missing, try filing a bug report with your > distribution to include the module or remove its meantion from this man > page. > If you experiance bugs, contact us at FIXME > > COPYRIGHT > Upstream is Free software. It is released under the terms of the > GNU GPL 2.0 or any later version. > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > |
|
From: Karl G. <kam...@in...> - 2006-12-08 14:00:56
|
Ryan Zeigler wrote: > That looks good, the only problem is, depending on what log modules are > shipped, thos categories may or may not be present. The actually available > categories are determined at runtime based on what modules are available. > > Thanks for the feedback, i have made a few changes to reflect it, along with a few other bits and pieces. update attached, kk > Ryan > On Friday 08 December 2006 08:04, Karl Goetz wrote: > >> hi all >> Now with switches! >> Still, feedback welcome :) >> kk >> -- Karl Goetz User of gNewSense: Free as in Freedom - http://www.gnewsense.org Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam Debian, The Universal Operating System - http://www.debian.org |
|
From: Ryan Z. <zei...@gm...> - 2006-12-08 13:29:13
|
That looks good, the only problem is, depending on what log modules are=20 shipped, thos categories may or may not be present. The actually available= =20 categories are determined at runtime based on what modules are available. Ryan On Friday 08 December 2006 08:04, Karl Goetz wrote: > hi all > Now with switches! > Still, feedback welcome :) > kk |
|
From: Karl G. <kam...@in...> - 2006-12-08 13:04:42
|
hi all Now with switches! Still, feedback welcome :) kk -- Karl Goetz User of gNewSense: Free as in Freedom - http://www.gnewsense.org Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam Debian, The Universal Operating System - http://www.debian.org |
|
From: Karl G. <kam...@in...> - 2006-12-08 12:42:43
|
hi all. Here is a start to a man page. I'm about to add launch switches. any other feedback would be good. kk -- Karl Goetz User of gNewSense: Free as in Freedom - http://www.gnewsense.org Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam Debian, The Universal Operating System - http://www.debian.org |
|
From: Mahangu W. <ma...@gm...> - 2006-12-08 00:59:31
|
Hi Juha, It looks fine man. Thanks a lot! I'll commit this now, and then you can svn checkout and test it yourself. :-) - Mahangu On 12/8/06, Juha Siltala <ju...@si...> wrote: > Hi, > > Here's my shot at a Finnish fi.po file. It's been a while since i > touched a .po file, I hope I got it right. Any problems, let me know! > > -- > Juha Siltala > http://siltala.net > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > > |
|
From: Juha S. <ju...@si...> - 2006-12-07 19:03:33
|
Hi, Here's my shot at a Finnish fi.po file. It's been a while since i touched a .po file, I hope I got it right. Any problems, let me know! -- Juha Siltala http://siltala.net |
|
From: John <so...@gm...> - 2006-12-04 01:16:40
|
Oki, this is going to be the last one for today, I promise. I just tested the stuff, and found one incoherent part. here is the new version. nite John >Man this is painstaking. Okay, now I *might* have it right. >>Woops, here is another try, tell me if it worked... >>Very strange I didn't attach the file. It's the fault of thunderbird! >>(no, really, I forgot :-S) >>Cheers >>John >>>Here is the hungarian translation for upstream.po, I really have no >idea >>>what to do with it, I just renamed it to *_hu.po. >>>Cheers! >>>John |
|
From: John <so...@gm...> - 2006-12-04 00:25:59
|
Man this is painstaking. Okay, now I *might* have it right. >Woops, here is another try, tell me if it worked... >Very strange I didn't attach the file. It's the fault of thunderbird! >(no, really, I forgot :-S) >Cheers >John >>Here is the hungarian translation for upstream.po, I really have no >idea >>what to do with it, I just renamed it to *_hu.po. >>Cheers! >>John |
|
From: John <so...@gm...> - 2006-12-03 23:34:00
|
Woops, here is another try, tell me if it worked... Very strange I didn't attach the file. It's the fault of thunderbird! (no, really, I forgot :-S) Cheers John >Here is the hungarian translation for upstream.po, I really have no >idea >what to do with it, I just renamed it to *_hu.po. >Cheers! >John |
|
From: John <so...@gm...> - 2006-12-03 12:28:38
|
Here is the hungarian translation for upstream.po, I really have no idea what to do with it, I just renamed it to *_hu.po. Cheers! John |
|
From: Mahangu W. <ma...@gm...> - 2006-12-01 02:42:59
|
Firstly, thank you Jason for the extensive research you've done on the subject. > So, the first issue is whether we want to use the stock buttons or > not. A third option would be to use stock buttons and write some > python that checks if a translation is available for the buttons. If > it isn't then they get replaced by regular buttons and we fetch the > strings from the translation file. This seems cumbersome but might be > possible. I'm still hoping that there is a better way to handle this, > maybe we can take a look at how other applications approach this > problem. We should be able to check for translations. Since this is has been more or less bumped to 0.2, I think we can spend some time really thinking about this. If others on the list voiced their opinions it would be easier to reach a wider consensus I think. Of course, we will also discuss this at the next developer meeting. > Kayak uses qt so the situation is a little different. Apparently, > translations for the stock buttons are available only for German and > French (actually 8 languages but they are not complete). So > currently, the plan is to just have Upstream translators translate all > of kayak's buttons. As I said on IRC, my stance on the matter is this - It's nice if our button translations were sent upstream to KDE/Gnome, but we shouldn't take such an approach at the price of our usability. We don't know how long translations will take to get in to the official releases, and we're not experienced translators by any means. Perhaps we should email the translators lists of the two WEs? Personally, I think we should translate the buttons by default for this release while simultaneously submitting translations for the buttons upstream. However, your approach of checking for translations and falling back to our own implementation works as well. I'm just wondering how much code we'd have to write, and if it will be worth the effort. Please let me reiterate that I _am_ for helping the community on the whole and would very much like to see these buttons translated at the source. I'm just not sure of the best way to go about this. Other thoughts / ideas are welcome. |
|
From: Jason R. <jas...@gm...> - 2006-11-30 14:46:48
|
Hi everyone, At this point, base, kayak, and canoe are almost ready to be translated. We came across one issue though. In Canoe, stock buttons are used such as "OK", "Next", etc. As far as translation is concerned, the advantage to using stock buttons is that the buttons automatically use the translation for the stock buttons (i.e. translators for Upstream do not have to worry about them). On the downside, if translations for the stock buttons are not available in a particular language that Upstream is translated for, then we end up with everything except the buttons getting translated. In the big picture, I think it makes sense that things like "Ok", and "Next" only get translated once and put into the gtk package. This is better than having translators translate these strings for every application that uses common buttons like these. Base also seems to operate similarly at the moment. That is, even without an upstream translation into, say Portuguese, the buttons like "OK" or "Cancel" will still be translated using some common translation to all applications that use dialog.py (not sure where these come from at the moment). So, the first issue is whether we want to use the stock buttons or not. A third option would be to use stock buttons and write some python that checks if a translation is available for the buttons. If it isn't then they get replaced by regular buttons and we fetch the strings from the translation file. This seems cumbersome but might be possible. I'm still hoping that there is a better way to handle this, maybe we can take a look at how other applications approach this problem. Kayak uses qt so the situation is a little different. Apparently, translations for the stock buttons are available only for German and French (actually 8 languages but they are not complete). So currently, the plan is to just have Upstream translators translate all of kayak's buttons. What does everyone think? |
|
From: Jason R. <jas...@gm...> - 2006-11-28 13:52:50
|
I agree with Ryan. We are not security experts, but we will fix security problems brought to our attention. Mahangu, would this list do as a contact? We could just consider all the devs as security contacts, until someone wants to handle these issues specifically. Any security issue would probably end up being discussed with all the devs anyway. On 11/28/06, Mahangu Weerasinghe <ma...@gm...> wrote: > Agreed. Yes, the new md5sum system is a welcome feature as we begin to > talk about Upstream and security. Well done Ryan! > > As far as security goes though, I think it's still useful to have an > official contact, someone for downstream to keep in touch with. I > dunno, what does everyone else think? > > On 11/28/06, Ryan Zeigler <zei...@gm...> wrote: > > Everyone, > > I think that the issue of security audits aren't particularly an issue. I > > mean, we have validation infrastructure in place, and I would just say to > > Brazil that we can guarantee fixes for any security issues that are found, > > but that we ourselves are not security experts. Furthermore, the codebase is > > sufficiently small and we have infrastructure in place to prevent the user > > from just randomly using log modules that will break their stuff. Anyway, > > what I'm saying is, for now, present it that we will fix any security > > problems that are found, but that we aren't particularly useful at finding > > them in the first place. Also, highlight the fact that our codebase is so > > small at this point that there isn't much that could happen. > > My 2c > > Ryan > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > opinions on IT & business topics through brief surveys - and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > _______________________________________________ > > Upstream-devel mailing list > > Ups...@li... > > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > > > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > |
|
From: Mahangu W. <ma...@gm...> - 2006-11-28 11:44:44
|
Agreed. Yes, the new md5sum system is a welcome feature as we begin to talk about Upstream and security. Well done Ryan! As far as security goes though, I think it's still useful to have an official contact, someone for downstream to keep in touch with. I dunno, what does everyone else think? On 11/28/06, Ryan Zeigler <zei...@gm...> wrote: > Everyone, > I think that the issue of security audits aren't particularly an issue. I > mean, we have validation infrastructure in place, and I would just say to > Brazil that we can guarantee fixes for any security issues that are found, > but that we ourselves are not security experts. Furthermore, the codebase is > sufficiently small and we have infrastructure in place to prevent the user > from just randomly using log modules that will break their stuff. Anyway, > what I'm saying is, for now, present it that we will fix any security > problems that are found, but that we aren't particularly useful at finding > them in the first place. Also, highlight the fact that our codebase is so > small at this point that there isn't much that could happen. > My 2c > Ryan > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > > |