Thread: Re: [Quickfix-developers] bugs, bug tracking, and release plans
Brought to you by:
orenmnero
Menu
▾
▴
quickfix-developers
|
From: <or...@qu...> - 2009-03-06 19:14:28
|
Hold on guys. We are still alive over here. I know that's it's been a while and I've neglected things for a bit. I really would like to avoid a fork, that would be messy. I think we need to talk about what the core issues that need to be addressed with the project and move forward from there. --oren > -------- Original Message -------- > Subject: Re: [Quickfix-developers] bugs, bug tracking, and release > plans > From: "Andrew Culross" <And...@Tw...> > Date: Fri, March 06, 2009 11:15 am > To: "'Mark T. Kennedy'" <mke...@di...>, "'Chuck Remes'" > <cre...@ma...> > Cc: 'quickfix developers' <qui...@li...> > > > QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > I'm wondering if the core developers have just moved over to the QuickFIX/J > implementation - seems like there is a little more going on over there . . . > > But yeah, I'd like to know if this is a dead-end as well. > > Andrew Culross > Direct +1 (914) 220-8849 > http://www.twofour.com/emaildisclaimer.aspx > > -----Original Message----- > From: Mark T. Kennedy [mailto:mke...@di...] > Sent: Friday, March 06, 2009 11:33 AM > To: Chuck Remes > Cc: quickfix developers > Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans > > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > > uh oh - the "f" word :-). but you may be right. drew et al, can you shed > some light on things? > /mark > > Chuck Remes wrote: > > On Mar 6, 2009, at 9:27 AM, Mark T. Kennedy wrote: > > > >> QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > >> QuickFIX Support: http://www.quickfixengine.org/services.html > >> > >> > >> the www.quickfixengine.org web site still points at the "Hacked by > >> the Hunter" bug tracking page. > >> no replacement has been forthcoming. nor have the bugs that i found > >> and fixed in 12.4, which > >> lead to the loss of messages and a blocked runtime, made it into any > >> release. > >> > >> can someone post a status message? what are the plans of the > >> primary developers? > > > > Two or three times a month there is a post to this list asking about > > new releases, getting bug fixes submitted and pulled into trunk, etc. > > There are rarely any responses from the core devs. The last release is > > going on 3 years ago. > > > > Time to fork. > > > > cr > > > > > > This communication and any attachments may contain confidential/proprietary > information and is intended for information purposes only. It is not an > invitation or offer to purchase interests from Diamondback. Any > representation to the contrary is unintentional. This communication is > intended only for the person(s) to whom it is addressed. If you are not the > intended recipient you are hereby notified that you have received this > document in error and that any review, dissemination, distribution, or > copying of this message or any attachments is not permitted. If you have > received this in error, please notify the sender immediately by e-mail and > delete this message. All e-mails sent to or received from this address will > be received by Diamondback's company e-mail system and is subject to > archival and possible review by someone other than the recipient. This > notice is automatically appended to each e-mail message leaving Diamondback. > > > ---------------------------------------------------------------------------- > -- > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: <or...@qu...> - 2009-03-10 22:15:49
|
Ok. I've read everyone's comments and will be addressing each one of them in a single email shortly. I agree that we badly need to get back in the bugtracking business. I've set up the sourceforge bugtracker. You will be required to have a sourceforge logon in order to make submissions. This should help with a lot of the security issues we have had in the past. You can click on the bugtracker link at quickfixengine.org or just go here: https://sourceforge.net/tracker2/?group_id=37535. I've setup separate repositories for bugs, feature requests, and patch submissions. Please add the suggestions you have given to the appropriate place. --oren |
|
From: Chuck R. <cre...@ma...> - 2009-03-09 16:09:07
|
On Mar 6, 2009, at 12:47 PM, or...@qu... wrote: > Hold on guys. We are still alive over here. I know that's it's > been a > while and I've neglected things for a bit. I really would like to > avoid > a fork, that would be messy. I think we need to talk about what the > core issues that need to be addressed with the project and move > forward > from there. > > --oren Oren, I'll take a first stab at listing a few things that I think are important to this list. Hopefully others will chime in. 1. A release that builds cleanly under 64-bit OS. 2. A release that builds cleanly on Debian, FreeBSD and OSX. These build issues *may* be related to gcc 4.3.x. Past emails to this list indicate there may have been patches submitted for these issues. 3. Some members of this list may deserve commit rights. A move from svn to git may streamline this a bit if you prefer to avoid giving "strangers" commit rights to the svn repository. With git, everyone's local repository is effectively a fork that can submit patches upstream. cr |
|
From: Andrew C. <And...@Tw...> - 2009-03-09 16:16:50
|
Some thoughts. 1. Latest integration of bug fixes into primary build 2. Little stuff that seems to be on the list frequently (rolling log files, encryption support) 3. Support for latest FIX releases (FastFIX, FIX5.0) Andrew Culross Direct +1 (914) 220-8849 http://www.twofour.com/emaildisclaimer.aspx -----Original Message----- From: Chuck Remes [mailto:cre...@ma...] Sent: Monday, March 09, 2009 12:09 PM To: or...@qu... Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy' Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans On Mar 6, 2009, at 12:47 PM, or...@qu... wrote: > Hold on guys. We are still alive over here. I know that's it's > been a > while and I've neglected things for a bit. I really would like to > avoid > a fork, that would be messy. I think we need to talk about what the > core issues that need to be addressed with the project and move > forward > from there. > > --oren Oren, I'll take a first stab at listing a few things that I think are important to this list. Hopefully others will chime in. 1. A release that builds cleanly under 64-bit OS. 2. A release that builds cleanly on Debian, FreeBSD and OSX. These build issues *may* be related to gcc 4.3.x. Past emails to this list indicate there may have been patches submitted for these issues. 3. Some members of this list may deserve commit rights. A move from svn to git may streamline this a bit if you prefer to avoid giving "strangers" commit rights to the svn repository. With git, everyone's local repository is effectively a fork that can submit patches upstream. cr |
|
From: Marcin G. <mar...@ar...> - 2009-03-10 12:45:52
|
Andrew Culross pisze: Hi, Speaking as local Polish programming company I'd also like to have a chance to send some patches we've done for 1.12.4 C++ mainly (64bit/new gcc/logs/Postgresql related/etc). If possible we can also offer our help in developing new features into QuickFix. Thanks, Marcin > QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > Some thoughts. > > 1. Latest integration of bug fixes into primary build > 2. Little stuff that seems to be on the list frequently (rolling log files, > encryption support) > 3. Support for latest FIX releases (FastFIX, FIX5.0) > > Andrew Culross > Direct +1 (914) 220-8849 > http://www.twofour.com/emaildisclaimer.aspx > > -----Original Message----- > From: Chuck Remes [mailto:cre...@ma...] > Sent: Monday, March 09, 2009 12:09 PM > To: or...@qu... > Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy' > Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans > > > On Mar 6, 2009, at 12:47 PM, or...@qu... wrote: > > >> Hold on guys. We are still alive over here. I know that's it's >> been a >> while and I've neglected things for a bit. I really would like to >> avoid >> a fork, that would be messy. I think we need to talk about what the >> core issues that need to be addressed with the project and move >> forward >> from there. >> >> --oren >> > > Oren, > > I'll take a first stab at listing a few things that I think are > important to this list. Hopefully others will chime in. > > 1. A release that builds cleanly under 64-bit OS. > > 2. A release that builds cleanly on Debian, FreeBSD and OSX. These > build issues *may* be related to gcc 4.3.x. Past emails to this list > indicate there may have been patches submitted for these issues. > > 3. Some members of this list may deserve commit rights. A move from > svn to git may streamline this a bit if you prefer to avoid giving > "strangers" commit rights to the svn repository. With git, everyone's > local repository is effectively a fork that can submit patches upstream. > > cr > > > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > |
|
From: Peter P. <pet...@ho...> - 2009-03-09 16:33:40
|
Dear Oren, My immediate vote (apart from the bug fixes, of course) is to have: 1. Separate target directories for different compiler versions. I have different active projects that use three versions of the Visual Studio compiler (7, 8 and 9), for example. The raw distribution gets horribly confused when all output directories are the same, so I have to hack the makefiles a lot to make everything live happily in its own space. I don;t want to have to repeat this process on every new release. 2. Add more robust versioning with build numbers, so that I can distinguish bug fix releases from ones that might change the defined behaviour (and therefore need a whole new folder tree). This probably won't mix too well if you are going to allow others to commit but I'd like to have some sort of idea of exactly which version is in the repo whenever I do a clean download. Yours, Dan > From: And...@Tw... > To: cre...@ma...; or...@qu... > Date: Mon, 9 Mar 2009 12:16:17 -0400 > CC: mke...@di...; qui...@li... > Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans > > QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > Some thoughts. > > 1. Latest integration of bug fixes into primary build > 2. Little stuff that seems to be on the list frequently (rolling log files, > encryption support) > 3. Support for latest FIX releases (FastFIX, FIX5.0) > > Andrew Culross > Direct +1 (914) 220-8849 > http://www.twofour.com/emaildisclaimer.aspx > > -----Original Message----- > From: Chuck Remes [mailto:cre...@ma...] > Sent: Monday, March 09, 2009 12:09 PM > To: or...@qu... > Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy' > Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans > > > On Mar 6, 2009, at 12:47 PM, or...@qu... wrote: > > > Hold on guys. We are still alive over here. I know that's it's > > been a > > while and I've neglected things for a bit. I really would like to > > avoid > > a fork, that would be messy. I think we need to talk about what the > > core issues that need to be addressed with the project and move > > forward > > from there. > > > > --oren > > Oren, > > I'll take a first stab at listing a few things that I think are > important to this list. Hopefully others will chime in. > > 1. A release that builds cleanly under 64-bit OS. > > 2. A release that builds cleanly on Debian, FreeBSD and OSX. These > build issues *may* be related to gcc 4.3.x. Past emails to this list > indicate there may have been patches submitted for these issues. > > 3. Some members of this list may deserve commit rights. A move from > svn to git may streamline this a bit if you prefer to avoid giving > "strangers" commit rights to the svn repository. With git, everyone's > local repository is effectively a fork that can submit patches upstream. > > cr > > > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers _________________________________________________________________ 25GB of FREE Online Storage – Find out more http://clk.atdmt.com/UKM/go/134665320/direct/01/ |
|
From: Mark T. K. <mke...@di...> - 2009-03-09 17:07:20
|
oren, you need to open things up a bit. you need an (unhackable :-) issue/bug tracking system. and you need to open up the repository to other developers. /mark Peter Piper wrote: > QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > > > ------------------------------------------------------------------------ > > Dear Oren, > > My immediate vote (apart from the bug fixes, of course) is to have: > > 1. Separate target directories for different compiler versions. I have > different active projects that use three versions of the Visual Studio > compiler (7, 8 and 9), for example. The raw distribution gets horribly > confused when all output directories are the same, so I have to hack the > makefiles a lot to make everything live happily in its own space. I > don;t want to have to repeat this process on every new release. > > 2. Add more robust versioning with build numbers, so that I can > distinguish bug fix releases from ones that might change the defined > behaviour (and therefore need a whole new folder tree). This probably > won't mix too well if you are going to allow others to commit but I'd > like to have some sort of idea of exactly which version is in the repo > whenever I do a clean download. > > Yours, > > Dan > >> From: And...@Tw... >> To: cre...@ma...; or...@qu... >> Date: Mon, 9 Mar 2009 12:16:17 -0400 >> CC: mke...@di...; qui...@li... >> Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans >> >> QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html >> QuickFIX Support: http://www.quickfixengine.org/services.html >> >> Some thoughts. >> >> 1. Latest integration of bug fixes into primary build >> 2. Little stuff that seems to be on the list frequently (rolling log > files, >> encryption support) >> 3. Support for latest FIX releases (FastFIX, FIX5.0) >> >> Andrew Culross >> Direct +1 (914) 220-8849 >> http://www.twofour.com/emaildisclaimer.aspx >> >> -----Original Message----- >> From: Chuck Remes [mailto:cre...@ma...] >> Sent: Monday, March 09, 2009 12:09 PM >> To: or...@qu... >> Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy' >> Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans >> >> >> On Mar 6, 2009, at 12:47 PM, or...@qu... wrote: >> >> > Hold on guys. We are still alive over here. I know that's it's >> > been a >> > while and I've neglected things for a bit. I really would like to >> > avoid >> > a fork, that would be messy. I think we need to talk about what the >> > core issues that need to be addressed with the project and move >> > forward >> > from there. >> > >> > --oren >> >> Oren, >> >> I'll take a first stab at listing a few things that I think are >> important to this list. Hopefully others will chime in. >> >> 1. A release that builds cleanly under 64-bit OS. >> >> 2. A release that builds cleanly on Debian, FreeBSD and OSX. These >> build issues *may* be related to gcc 4.3.x. Past emails to this list >> indicate there may have been patches submitted for these issues. >> >> 3. Some members of this list may deserve commit rights. A move from >> svn to git may streamline this a bit if you prefer to avoid giving >> "strangers" commit rights to the svn repository. With git, everyone's >> local repository is effectively a fork that can submit patches upstream. >> >> cr >> >> >> >> >> > ------------------------------------------------------------------------------ >> Open Source Business Conference (OSBC), March 24-25, 2009, San > Francisco, CA >> -OSBC tackles the biggest issue in open source: Open Sourcing the > Enterprise >> -Strategies to boost innovation and cut costs with open source > participation >> -Receive a $600 discount off the registration fee with the source > code: SFAD >> http://p.sf.net/sfu/XcvMzF8H >> _______________________________________________ >> Quickfix-developers mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > ------------------------------------------------------------------------ > Share your photos with Windows Live Photos – Free. Try it Now! > <http://clk.atdmt.com/UKM/go/134665338/direct/01/> > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > > > ------------------------------------------------------------------------ > > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers This communication and any attachments may contain confidential/proprietary information and is intended for information purposes only. It is not an invitation or offer to purchase interests from Diamondback. Any representation to the contrary is unintentional. This communication is intended only for the person(s) to whom it is addressed. If you are not the intended recipient you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message or any attachments is not permitted. If you have received this in error, please notify the sender immediately by e-mail and delete this message. All e-mails sent to or received from this address will be received by Diamondback's company e-mail system and is subject to archival and possible review by someone other than the recipient. This notice is automatically appended to each e-mail message leaving Diamondback. |
|
From: Alexey Z. <ale...@in...> - 2009-03-09 20:49:10
|
The bug tracker must be fixed first. There are a lot of stuff and we need to put it together. Peter Piper wrote: > Dear Oren, > > My immediate vote (apart from the bug fixes, of course) is to have: > > 1. Separate target directories for different compiler versions. I have > different active projects that use three versions of the Visual Studio > compiler (7, 8 and 9), for example. The raw distribution gets horribly > confused when all output directories are the same, so I have to hack > the makefiles a lot to make everything live happily in its own space. > I don;t want to have to repeat this process on every new release. > > 2. Add more robust versioning with build numbers, so that I can > distinguish bug fix releases from ones that might change the defined > behaviour (and therefore need a whole new folder tree). This probably > won't mix too well if you are going to allow others to commit but I'd > like to have some sort of idea of exactly which version is in the repo > whenever I do a clean download. > > Yours, > > Dan > > > From: And...@Tw... > > To: cre...@ma...; or...@qu... > > Date: Mon, 9 Mar 2009 12:16:17 -0400 > > CC: mke...@di...; > qui...@li... > > Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans > > > > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > > QuickFIX Support: http://www.quickfixengine.org/services.html > > > > Some thoughts. > > > > 1. Latest integration of bug fixes into primary build > > 2. Little stuff that seems to be on the list frequently (rolling log > files, > > encryption support) > > 3. Support for latest FIX releases (FastFIX, FIX5.0) > > > > Andrew Culross > > Direct +1 (914) 220-8849 > > http://www.twofour.com/emaildisclaimer.aspx > > > > -----Original Message----- > > From: Chuck Remes [mailto:cre...@ma...] > > Sent: Monday, March 09, 2009 12:09 PM > > To: or...@qu... > > Cc: And...@Tw...; 'quickfix developers'; 'Mark T. Kennedy' > > Subject: Re: [Quickfix-developers] bugs, bug tracking, and release plans > > > > > > On Mar 6, 2009, at 12:47 PM, or...@qu... wrote: > > > > > Hold on guys. We are still alive over here. I know that's it's > > > been a > > > while and I've neglected things for a bit. I really would like to > > > avoid > > > a fork, that would be messy. I think we need to talk about what the > > > core issues that need to be addressed with the project and move > > > forward > > > from there. > > > > > > --oren > > > > Oren, > > > > I'll take a first stab at listing a few things that I think are > > important to this list. Hopefully others will chime in. > > > > 1. A release that builds cleanly under 64-bit OS. > > > > 2. A release that builds cleanly on Debian, FreeBSD and OSX. These > > build issues *may* be related to gcc 4.3.x. Past emails to this list > > indicate there may have been patches submitted for these issues. > > > > 3. Some members of this list may deserve commit rights. A move from > > svn to git may streamline this a bit if you prefer to avoid giving > > "strangers" commit rights to the svn repository. With git, everyone's > > local repository is effectively a fork that can submit patches upstream. > > > > cr > > > > > > > > > > > ------------------------------------------------------------------------------ > > Open Source Business Conference (OSBC), March 24-25, 2009, San > Francisco, CA > > -OSBC tackles the biggest issue in open source: Open Sourcing the > Enterprise > > -Strategies to boost innovation and cut costs with open source > participation > > -Receive a $600 discount off the registration fee with the source > code: SFAD > > http://p.sf.net/sfu/XcvMzF8H > > _______________________________________________ > > Quickfix-developers mailing list > > Qui...@li... > > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > ------------------------------------------------------------------------ > Share your photos with Windows Live Photos – Free. Try it Now! > <http://clk.atdmt.com/UKM/go/134665338/direct/01/> |
|
From: Michael F. <mic...@gm...> - 2009-03-12 11:57:10
|
Hi Oren (and other), I would like to add my voice behind a clean install of a 64-bit version (as put forward by cre...@ma...) - especially for us *nix users. I too get the following errors when compiling Quickfix with Python (same as qui...@se...) : > QuickfixPython.cpp: In function 'int SWIG_Python_ConvertFunctionPtr > (PyObject*, void**, swig_type_info*)': > QuickfixPython.cpp:2052: error: invalid conversion from 'const char*' > to 'char*' and there is a reason I want to compile in the Python API... my C/C++ isn't too strong anymore. I have added this under the new Sourceforge bugtracking as a bug. Michael On Mon, Mar 9, 2009 at 6:08 PM, Chuck Remes <cre...@ma...> wrote: > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > > On Mar 6, 2009, at 12:47 PM, or...@qu... wrote: > > > Hold on guys. We are still alive over here. I know that's it's > > been a > > while and I've neglected things for a bit. I really would like to > > avoid > > a fork, that would be messy. I think we need to talk about what the > > core issues that need to be addressed with the project and move > > forward > > from there. > > > > --oren > > Oren, > > I'll take a first stab at listing a few things that I think are > important to this list. Hopefully others will chime in. > > 1. A release that builds cleanly under 64-bit OS. > > 2. A release that builds cleanly on Debian, FreeBSD and OSX. These > build issues *may* be related to gcc 4.3.x. Past emails to this list > indicate there may have been patches submitted for these issues. > > 3. Some members of this list may deserve commit rights. A move from > svn to git may streamline this a bit if you prefer to avoid giving > "strangers" commit rights to the svn repository. With git, everyone's > local repository is effectively a fork that can submit patches upstream. > > cr > > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, > CA > -OSBC tackles the biggest issue in open source: Open Sourcing the > Enterprise > -Strategies to boost innovation and cut costs with open source > participation > -Receive a $600 discount off the registration fee with the source code: > SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X