Menu
▾
▴
ayttm-devel — devlopers list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(264) |
May
(184) |
Jun
(34) |
Jul
(41) |
Aug
(13) |
Sep
(47) |
Oct
(48) |
Nov
(19) |
Dec
(17) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(37) |
Feb
(6) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
(21) |
Feb
(28) |
Mar
(15) |
Apr
(56) |
May
(11) |
Jun
(6) |
Jul
(22) |
Aug
(41) |
Sep
|
Oct
(30) |
Nov
(6) |
Dec
(8) |
| 2008 |
Jan
|
Feb
(1) |
Mar
(5) |
Apr
|
May
(4) |
Jun
(35) |
Jul
(21) |
Aug
(22) |
Sep
|
Oct
(21) |
Nov
(36) |
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(7) |
Apr
(3) |
May
(10) |
Jun
(1) |
Jul
(20) |
Aug
(29) |
Sep
(21) |
Oct
(14) |
Nov
(23) |
Dec
(5) |
| 2010 |
Jan
|
Feb
(6) |
Mar
(2) |
Apr
(16) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
|
From: Siddhesh P. <sid...@gm...> - 2009-11-05 07:50:31
|
Hi, The ayttm-devel list is no open for anyone who wants to subscribe. You can do that here: https://lists.sourceforge.net/lists/listinfo/ayttm-devel Please note that only discussions relevant to hacking on ayttm should be posted on this list. Any configuration related discussions or questions need to remain on the ayttm-users list. Discussions on the future course as well as current development progress of ayttm are also done on this list, so anyone (distribution package maintainers) who wants to track this may want to subscribe too. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Philip T. <phi...@gm...> - 2009-11-05 04:33:49
|
2009/11/4 Siddhesh Poyarekar <sid...@gm...>: > $Subject > > There's quite a bit of development related discussion happening on the > -users list which will fit in better over here. I have also got a few > requests for inclusion into the devel list. I don't have the list > admin password to do anything worthwhile with the mailing lists. It > would be easier if they could go sign up for themselves. If you have project admin, then you can change the list admin password from the sourceforge UI. go ahead and do it. I don't really remember the password anyway. |
|
From: Kartik M. <kar...@gm...> - 2009-11-05 03:56:12
|
On Thu, Nov 5, 2009 at 8:30 AM, Siddhesh Poyarekar <sid...@gm...> wrote: >> See: Debian bug, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553967 > > I have signed up for notifications for the debian package, so I got > this. I'll work on it today or tomorrow. Did not have any time for > ayttm so far this week. Nice and no issue. It is minor bug and it is my duty to notify upsteam :) -- Cheers, Kartik Mistry | 0xD1028C8D | IRC: kart_ Debian GNU/Linux Developer | Identica: @kartikm Blogs: {ftbfs, kartikm}.wordpress.com |
|
From: Siddhesh P. <sid...@gm...> - 2009-11-05 03:03:59
|
$Subject There's quite a bit of development related discussion happening on the -users list which will fit in better over here. I have also got a few requests for inclusion into the devel list. I don't have the list admin password to do anything worthwhile with the mailing lists. It would be easier if they could go sign up for themselves. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Siddhesh P. <sid...@gm...> - 2009-11-05 03:00:51
|
On Wed, Nov 4, 2009 at 10:37 PM, Kartik Mistry <kar...@gm...> wrote: > $subject > > See: Debian bug, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553967 > > More explanation: > http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking > I have signed up for notifications for the debian package, so I got this. I'll work on it today or tomorrow. Did not have any time for ayttm so far this week. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Kartik M. <kar...@gm...> - 2009-11-04 17:07:59
|
$subject See: Debian bug, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553967 More explanation: http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking Thanks :) -- Cheers, Kartik Mistry | 0xD1028C8D | IRC: kart_ Debian GNU/Linux Developer | Identica: @kartikm Blogs: {ftbfs, kartikm}.wordpress.com |
|
From: Siddhesh P. <sid...@gm...> - 2009-10-30 13:53:05
|
Hi, Ayttm 0.6.1 is out. You can get the sources for the latest release here: http://ayttm.sourceforge.net/files.php Report bugs: http://sourceforge.net/tracker/?group_id=77614&atid=550744 Request Features: http://sourceforge.net/tracker/?group_id=77614&atid=550747 Submit patches: http://sourceforge.net/tracker/?group_id=77614&atid=550746 This release brings in a number of bug fixes along with a few features: * Fix a number of MSN related crashes * Personal status messages support for MSN * Fix a Yahoo authentication bug * Yahoo File Transfer * MSN Invisible login preference finally works again * Fix the "Check new release" button * Fix date/time bugs in the tool tips * Notifications in chat windows * Autotranslate is fixed. Uses Google Translate now * SMTP and Livejournal should be working again See the complete Changelog here: http://ayttm.git.sourceforge.net/git/gitweb.cgi?p=ayttm/ayttm;a=blob;f=ChangeLog;h=9e090ace2c35a722d2dc4a301215e79cef359e38;hb=HEAD -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Siddhesh P. <sid...@gm...> - 2009-10-29 19:08:49
|
On Thu, Oct 29, 2009 at 10:31 PM, Philip Tellis <phi...@gm...> wrote: >>> Doesn't match with the protocol release cycles of all the vendors we support. >>> >> >> When do protocol updates typically happen? > > At random. > And that matches exactly with our current release model ;) Alright, you've taken away my enthusiasm for monthly releases. Let's just make it 'often enough' then. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Philip T. <phi...@gm...> - 2009-10-29 17:01:40
|
2009/10/29 Siddhesh Poyarekar <sid...@gm...>: > On Thu, Oct 29, 2009 at 10:17 PM, Philip Tellis <phi...@gm...> wrote: >>> And speaking of update releases, I was thinking on the lines of a more >>> planned update release model. How does the last week of every month >>> sound? That will go well with the fact that we are now in the last >>> week of this month ;) >> >> Doesn't match with the protocol release cycles of all the vendors we support. >> > > When do protocol updates typically happen? At random. |
|
From: Siddhesh P. <sid...@gm...> - 2009-10-29 16:56:32
|
On Thu, Oct 29, 2009 at 10:17 PM, Philip Tellis <phi...@gm...> wrote: >> And speaking of update releases, I was thinking on the lines of a more >> planned update release model. How does the last week of every month >> sound? That will go well with the fact that we are now in the last >> week of this month ;) > > Doesn't match with the protocol release cycles of all the vendors we support. > When do protocol updates typically happen? -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Philip T. <phi...@gm...> - 2009-10-29 16:48:26
|
2009/10/29 Siddhesh Poyarekar <sid...@gm...>: > And speaking of update releases, I was thinking on the lines of a more > planned update release model. How does the last week of every month > sound? That will go well with the fact that we are now in the last > week of this month ;) Doesn't match with the protocol release cycles of all the vendors we support. |
|
From: Siddhesh P. <sid...@gm...> - 2009-10-29 15:38:58
|
On Thu, Oct 29, 2009 at 1:12 PM, Siddhesh Poyarekar <sid...@gm...> wrote: > Hi, > > I'll be doing the release today evening. I'll push the ChangeLog into > git before I do that. Please let me know if anyone has a problem with > this. > Ok, a couple of trivial issues while making the ChangeLog, so I'll have to push this to tomorrow: 1) Date formatting to keep rpmbuild happy. I think I can get this one right eventually with some scripting on top of 'git log'. I might lose out on the time factor though, since rpmbuild is really finicky and I've not been able to get the combo exactly right as yet. 2) File list for each commit. I'm not sure if this is necessary anymore. I am planning to replace it with the commit hash, which can be directly searchable in the source tree as well as in the browsable source tree online. Anyone thinks this is a bad idea? I'm trying to eliminate the need to write the ChangeLog every time we commit and have it generated automatically instead. git makes things completely decentralized, so maintaining a central ChangeLog does not seem a great idea anymore. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Siddhesh P. <sid...@gm...> - 2009-10-29 07:43:10
|
Hi, I'll be doing the release today evening. I'll push the ChangeLog into git before I do that. Please let me know if anyone has a problem with this. Post 0.6.1, me and Piotr will be starting work on a xmpp protocol, which will be a rewrite of the jabber plugin, but make it generic. The primary aim is to allow for wrappers around xmpp to make new jabber (jabber.com/org) and gtalk plugins. This way users will not have to manually configure gtalk/jabber on their systems. The aim is to make the wrapper plugins as light as possible. I'll clone another repository on sourceforge for this so that it does not come in the way of more update releases or any other work that may (hopefully) happen at FOSS.in. Merging back would be fairly simple since git can handle them better. And speaking of update releases, I was thinking on the lines of a more planned update release model. How does the last week of every month sound? That will go well with the fact that we are now in the last week of this month ;) -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Siddhesh P. <sid...@gm...> - 2009-10-21 10:40:09
|
Hi, FOSS.IN[1] workouts are a good way to get a lot of real work done. The FOSS.IN/2009 Call for Participation is out and we're putting in a workout proposal this year too. We did a submission last year[2] but it was not accepted. We have since managed to take care of a lot of last years wish list with 0.6.0. There are still some remaining, and based on that and a few new ones, here's a list of TODOs for the ayttm workout for FOSS.IN/2009: 1. Revive the Windows port. This should be a little easier than before due the fact that a lot of networking code has now been modularized into a single library 2. MSN File Transfer 3. A nice clean smiley set in MNG/PNG format 4. Icons 5. Update translations 6. Implement name completion in chat rooms 7. Package ayttm for $MY_FAVOURITE_DISTRO 8. Port ayttm to $MY_FAVOURITE_OS Prerequisites 0. Register as a delegate at FOSS.IN/2009 Other than that, the most important prerequisite to participating in this session is to have a prior idea of what you're planning to do. A prior study of the code base would only make things easier. Other prerequisites vary for the tasks and can be mapped by serial number: 1. Knowledge of build tools for Windows. Programming: C/C++, gtk2, glib2 2. C/C++, wireshark dump/tcpdump analysis 3. An eye for design. Knowledge of FOSS design tools (gimp, inkscape, etc.) 4. An eye for design. Knowledge of FOSS design tools (gimp, inkscape, etc.) 5. Should know how to write/update translations 6. C/C++, gtk2, glib2 7. Packaging guidlines for $MY_FAVOURITE_DISTRO. Basic knowledge of building autotools based applications 8. Knowledge of build tool chain for $MY_FAVOURITE_OS There is a post on the ayttm community journal[3], which will track the progress of the workout. [1] http://foss.in [2] http://community.livejournal.com/ayttm/8081.html [3] http://community.livejournal.com/ayttm/10165.html -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Philip T. <phi...@gm...> - 2009-10-17 17:36:55
|
2009/10/17 Siddhesh Poyarekar <sid...@gm...>: > Hi all, > > Here's a quick look at the list of things that need someone to pitch in for: > > 1) Bring the windows port up to date > 2) Graphics, screenshots and new smileys > 3) Documentation and website maintenance > 4) Translation updates > > I want to know if we (can) have owners for any of these tasks right > now because I am planning to put out a call for contributors in a > couple of days for things that do not have owners. if you don't find anyone, then a hackathon at foss.in would be a good idea. |
|
From: Siddhesh P. <sid...@gm...> - 2009-10-17 17:33:05
|
Hi all, Here's a quick look at the list of things that need someone to pitch in for: 1) Bring the windows port up to date 2) Graphics, screenshots and new smileys 3) Documentation and website maintenance 4) Translation updates I want to know if we (can) have owners for any of these tasks right now because I am planning to put out a call for contributors in a couple of days for things that do not have owners. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Philip T. <phi...@gm...> - 2009-10-10 19:07:54
|
It's for users who don't know what a core dump is. On 10/10/09, Siddhesh Poyarekar <sid...@gm...> wrote: > On Sat, Oct 10, 2009 at 3:49 PM, 2134918 <21...@gm...> wrote: >> The crash dialog makes it easier to report bugs an even when it >> doesn't provide any useful information, we at least get kind of bug >> report. Maybe we should improve it instead? >> > > I guess. But I don't see how we can make it any better. I guess I'll > just have to look a little harder. > > > -- > Siddhesh Poyarekar > http://siddhesh.in > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Ayttm-devel mailing list > Ayt...@li... > https://lists.sourceforge.net/lists/listinfo/ayttm-devel > -- hello world |
|
From: Siddhesh P. <sid...@gm...> - 2009-10-10 10:38:53
|
On Sat, Oct 10, 2009 at 3:49 PM, 2134918 <21...@gm...> wrote: > The crash dialog makes it easier to report bugs an even when it > doesn't provide any useful information, we at least get kind of bug > report. Maybe we should improve it instead? > I guess. But I don't see how we can make it any better. I guess I'll just have to look a little harder. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: 2134918 <21...@gm...> - 2009-10-10 10:20:18
|
The crash dialog makes it easier to report bugs an even when it doesn't provide any useful information, we at least get kind of bug report. Maybe we should improve it instead? |
|
From: Siddhesh P. <sid...@gm...> - 2009-10-10 05:41:49
|
Hi, The crash dialog seems to be pretty much reinventing the wheel. We can get much more useful information with an actual core dump rather than just the backtrace without debugging symbols. Can we get rid of it? -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Siddhesh P. <sid...@gm...> - 2009-09-19 14:30:27
|
Hi, I've copied the repository from cvs to git. You can view the web version here: http://ayttm.git.sourceforge.net I have tested a commit and it seems to be working fine for me. From the membership page, everyone seems to have access, so please let me know if anyone faces any problems. One thing I am yet to figure out is how to have an email sent for each git push. This is a good starter to know how to make your first commit: http://www.kernel.org/pub/software/scm/git/docs/user-manual.html The repository URL for read/write access is: ssh://<sf.net username>@ayttm.git.sourceforge.net/gitroot/ayttm/ayttm -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Siddhesh P. <sid...@gm...> - 2009-09-19 03:45:19
|
On Tue, Sep 15, 2009 at 8:03 PM, Siddhesh Poyarekar <sid...@gm...> wrote: > > I'll start with modules. > Ok, Piotr did all of it at once. I'm starting with the git move now. Should be done by tomorrow. It does not look like the CVS repository will be lost by the move. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Siddhesh P. <sid...@gm...> - 2009-09-15 14:33:21
|
On Tue, Sep 15, 2009 at 4:25 PM, 2134918 <21...@gm...> wrote: > I have nothing against moving to git, despite of the fact that I will > have to learn it. By the way, we could reformat source files to look > better. If you think that it's a good idea, we will have to choose > coding style and reformat every file with chosen style before we move > to git. +1. We follow this ;) http://ayttm.cvs.sf.net/viewvc/ayttm/ayttm/doc/CODING_STYLE?revision=1.1&view=markup I'll start with modules. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: 2134918 <21...@gm...> - 2009-09-15 10:56:10
|
I have nothing against moving to git, despite of the fact that I will have to learn it. By the way, we could reformat source files to look better. If you think that it's a good idea, we will have to choose coding style and reformat every file with chosen style before we move to git. |
|
From: Siddhesh P. <sid...@gm...> - 2009-09-15 09:59:18
|
On Tue, Sep 15, 2009 at 2:49 PM, Kartik Mistry <kar...@gm...> wrote: > On Tue, Sep 15, 2009 at 2:04 PM, Siddhesh Poyarekar > <sid...@gm...> wrote: >> I was wondering if it makes sense for us to move to git instead on SF. >> There are two reasons for my asking on these lines: > > +1 > > Where we are going to host it? github? It is also known for `downtime`. I was actually asked if we wanted to move to fedorahosted, but I am thinking on the lines of the git repository at SF.net. -- Siddhesh Poyarekar http://siddhesh.in |
24 messages has been excluded from this view by a project administrator.