Re: [vimplugin-devel] Current state of the project
David Terei
Sebastian Menge wrote:
> How can we join forces? We are at least four (more or less active)
> developers: Martin, Nageswar, David and myself. That sounds like a fine
> little team ...
Really two questions I guess:
1) Who's hosting?
2) Who's Code?
1.
Comes down to SourceForge (SF) vs Google Code (GC) a little so here is
my comparison of the two:
Basically SF has more features and flexibility but also is more complex
and requires more work to maintain because of this. Google Code is
simpler but less power.
- SF requires a fairly detailed registration of a project and approval
by a SF staff, GC is simple and instant approval.
- Both have SVN: pretty much exactly the same. (Google code only
offers SVN)
- Web space: SF has own web space area where you can put whatever you
like and supports PHP and some other CGI stuff from. GC doesn't have any
web space but instead provides you with a simple Wiki.
- File Downloads: SF uses ftp to upload your files and supports
grouping of files and associating a group with a version number. GC uses
a simple web page upload tool and doesn't have any concept of versions,
so you just use the download title to tell users. Uses tags to describe
the download (e.g a 'featured' tag makes the download appear on the
front page and a 'depreciated' tag hides them from the download lists
default view).
- Development Support tools: Both have issue trackers, fairly
comparable, but I find GC nicer with looks and the way it easily
supports commenting/conversations on items. SF has mailing lists, GC
uses Google groups for mailing lists. These are nicer IMHO since they
have a great web based interface which makes them like a forum. SF has
forums, GC doesn't but Google groups can server both roles well.
I would say I prefer GC, I have some bad memories of using CVS with SF
before they brought out SVN. The only area SF beats GC in is that they
provide your own web space while GC just provides a simple wiki. (Not
having FTP support for uploading files would be an issue for larger
projects as well but not for us).
So for me the web space is the only issue. If we were creating something
more graphical or for average users I would say SF since the website
would be fairly important. But since its an application for developers,
the look isn't as important.
Other issue is though that vimplugin has a lot more profile while eeedit
has virtually none.
2.
Our code is a logical continuation of Sebastian code. (Not the one using
a terminal emulator, but a new experimental version he started working on).
It uses the netbeans protocol supported by Vim to communicate between
Eclipse and Vim. I would think that there is no question between
Sebastian's code and eeedits code since as I said its a continuation.
Not sure about Martin's code, I will have a look at it when I have time.
I would think most likely it would make sense to work from our code base
but I will have a look at Martin's work first.
Also, I have forwarded all the emails from this thread to eeedit's
mailing list so that hopefully the other developers can weigh in on the
issue. There are three of us, Nageshwar M, Edward L. Fox (very recently
joined) and myself.
Best regards,
David Terei
> Sebastian.
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> vimplugin-devel mailing list
> vimplug...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/vimplugin-devel
>
Martin Krischik
I am here now as well ;-)
On 20 Sep., 02:49, David Terei <davidte...@gmail.com> wrote:
> Hey Sebastian and Martin,
>
> Sebastian Menge wrote:
> > How can we join forces? We are at least four (more or less active)
> > developers: Martin, Nageswar, David and myself. That sounds like a fine
> > little team ...
>
> Really two questions I guess:
>
> 1) Who's hosting?
>
> 2) Who's Code?
>
> 1.
> Comes down to SourceForge (SF) vs Google Code (GC) a little so here is
> my comparison of the two:
>
> - SF requires a fairly detailed registration of a project and approval
> by a SF staff, GC is simple and instant approval.
No Prob as we allready got two projects ;-)
> - Web space: SF has own web space area where you can put whatever you
> like and supports PHP and some other CGI stuff from. GC doesn't have any
> web space but instead provides you with a simple Wiki.
vimPlugin uses PmWiki anyway ;-) - but that will need a backup
strategy,
> - File Downloads: SF uses ftp to upload your files and supports
> grouping of files and associating a group with a version number. GC uses
> a simple web page upload tool and doesn't have any concept of versions,
> so you just use the download title to tell users. Uses tags to describe
> the download (e.g a 'featured' tag makes the download appear on the
> front page and a 'depreciated' tag hides them from the download lists
> default view).
If the project becomes larger that will become an issue.
> - Development Support tools: Both have issue trackers, fairly
> comparable, but I find GC nicer with looks and the way it easily
> supports commenting/conversations on items. SF has mailing lists, GC
> uses Google groups for mailing lists. These are nicer IMHO since they
> have a great web based interface which makes them like a forum. SF has
> forums, GC doesn't but Google groups can server both roles well.
I always use Google groups in "forum" mode - I just don't like it when
my mailbox is filled up with mailing list. Mind you: usenet is on
place 1.
> I would say I prefer GC, I have some bad memories of using CVS with SF
> before they brought out SVN. The only area SF beats GC in is that they
> provide your own web space while GC just provides a simple wiki. (Not
> having FTP support for uploading files would be an issue for larger
> projects as well but not for us).
I prefer SF since we already got an project there and there are a lot
of important Vim projects on SF as well.
> Other issue is though that vimplugin has a lot more profile while eeedit
> has virtually none.
Yes, you need to improve on marketing. If I had found about eeedit I
might not have started my on plugin. Yes I heard about you in
conjunction with "summer of code" but quickly forgot all about it. And
when Eclipse came into my live googleing for "vim eclipse plugin" did
not put you on the list :-( . Sorry to tell.
Marketing is also the reason why I did not start a new project but
rather asked to join vimplugin. So users can find me more easily.
> 2.
> Our code is a logical continuation of Sebastian code. (Not the one using
> a terminal emulator, but a new experimental version he started working on).
>
> It uses the netbeans protocol supported by Vim to communicate between
> Eclipse and Vim. I would think that there is no question between
> Sebastian's code and eeedits code since as I said its a continuation.
> Not sure about Martin's code, I will have a look at it when I have time.
Mine is just a few days old and and nothing to should about :-(. it is
based around a GVim Server - mainly because that is the technology
which usually works best when integrating Vim as an external editor
into any application.
> I would think most likely it would make sense to work from our code base
> but I will have a look at Martin's work first.
Indeed.
Martin
Edward L. Fox
On 9/20/07, Martin Krischik <kris...@users.sourceforge.net> wrote:
>
> Hallo,
>
> I am here now as well ;-)
Well, let vote.
Personally speaking I prefer GC. Because SF is much slower than GC for
me to access and I even can't reach SF timely.
>
> [...]
Regards,
Edward L. Fox
Nageshwar M
I have no problem moving to sf.net, it has many features and has a
large user community. I even have no problem with renaming the
project. As you now, many people don't know about googlecode.com. GC
supports all the features but with minimum functionality. But the
problem is, we already hosted the project and created groups, issues
and many things on GC. Moving all these things over sf.net is some
what time taking and also we used the word `eeedit` many times in the
code. Anyway they also willing to continue work on our code. So,
instead of moving, lets request vimplugin people to join our
community. I don't want two projects to exist with same objective.
Personally I too prefer GC, for its simple user interface.
I have another argument also. The actual objective is to design a
plugin for eclipse that supports multiple external editors like vim,
xemacs etc., So, is the name vimplugin suits the objective ?
--
Best Regards,
Nageshwar M.
Edward L. Fox
On 9/20/07, Nageshwar M <whatis...@gmail.com> wrote:
>
> Hi Friends,
>
> I have no problem moving to sf.net, it has many features and has a
> large user community. I even have no problem with renaming the
> project. As you now, many people don't know about googlecode.com. GC
> supports all the features but with minimum functionality. But the
> problem is, we already hosted the project and created groups, issues
> and many things on GC. Moving all these things over sf.net is some
> what time taking and also we used the word `eeedit` many times in the
> code. Anyway they also willing to continue work on our code. So,
> instead of moving, lets request vimplugin people to join our
> community. I don't want two projects to exist with same objective.
> Personally I too prefer GC, for its simple user interface.
I don't think renaming could be a big problem to this project - it
contains only 2000 lines. We can easily replace all the "eeedit",
"EeEdit", "Eeedit"... to whatever within 1 minute.
I've stored all the svn history in my local repository. If you think
it's necessary, I can replay all the project history to any new
repository. However, IMHO I don't think the history is quite
important.
And the mailing list. We don't need to merge the archive of the two
mailing list. In the future, we can merge the two mailing list
together by some simple settings. The result is, every member to each
mailing list can still send mails to their own mailing list, and the
mail will be displayed in both lists.
So, don't care too much about the migrating issues, just merge,
friends, just merge. Personally I prefer to host the merge project at
GC. But SF also looks good to me.
>
> I have another argument also. The actual objective is to design a
> plugin for eclipse that supports multiple external editors like vim,
> xemacs etc., So, is the name vimplugin suits the objective ?
Any better suggestion? NetBeansPlugin?
Personally speaking, I'd like to keep the current name. I don't think
we can easily support another text editor with no effort after we
finish the vimplugin. NetBeans is far from enough. In order to make
the text editor work properly, we have to compose some
editor-specified script to help the plugin working on Eclipse side. So
the plugin will no longer be "text-independent".
>
> --
> Best Regards,
> Nageshwar M.
>
>
I hate this footnote. Can any one who has the privilege remove this?
>
>
Best regards,
Edward L. Fox
Nageshwar M
>
> I don't think renaming could be a big problem to this project - it
> contains only 2000 lines. We can easily replace all the "eeedit",
> "EeEdit", "Eeedit"... to whatever within 1 minute.
>
> I've stored all the svn history in my local repository. If you think
> it's necessary, I can replay all the project history to any new
> repository. However, IMHO I don't think the history is quite
> important.
>
I considered file names also.. :-) If we rename the files, we will
lose the history. anyway thats not a big issue. We know how to revert
back if a problem arises.
> And the mailing list. We don't need to merge the archive of the two
> mailing list. In the future, we can merge the two mailing list
> together by some simple settings. The result is, every member to each
> mailing list can still send mails to their own mailing list, and the
> mail will be displayed in both lists.
>
So, are you suggesting to continue with two names for the same project
? I would like to have a single project, single name and a single
host.
> Personally speaking, I'd like to keep the current name. I don't think
> we can easily support another text editor with no effort after we
> finish the vimplugin. NetBeans is far from enough. In order to make
> the text editor work properly, we have to compose some
> editor-specified script to help the plugin working on Eclipse side. So
> the plugin will no longer be "text-independent".
>
I too, I like the present name eeedit. what I tried to say is eeedit
suits the project very best.
atleast our plugin supports other editors upto some extent, if we
concentrate on that issue.
But lets not bother about those things for now. Lets make it perfect for vim.
So, what shall we do ? All three of us want to stay here on GC.
Sebastian claiming the following as the advantages with the sf. This
message was sent to the guy.. martin.
---------------
I never used google code. It looks nice, but I feel more comfortable
with sf.net:
1) larger global user base
2) shell access: e.g. hosting the update site is easier with shell
access
3) free choice of homepage (static, wiki, etc: php and mysql
enabled) (btw I'd like to rework that wiki soon ...)
4) administration fairly easy. (I could not find a document about
features of google code ...)
But I think this is not a technical issue: The code is free and
everyone can do with it what he likes.
For me the most important thing is to keep people together. So I would
suggest to stay here and reimport your work, rather than move to a new
place, a new name etc. We have this list (40 members),
http://vimplugin.org, a http://freshmeat.net entry etc. So I guess
'vimplugin' has quite a bit of infrastructure and popularity.
For me it seems also logical to stay here, because your work builds up
on existing code. But that impression may be too subjective :-)
Sebastian.
PS I looked into the code last night. It works like a charm :-) What
new features are there?
---------------
lets discuss with them also. that will solve the problem.
Edward L. Fox
On 9/20/07, Nageshwar M <whatis...@gmail.com> wrote:
> [...]
>
> I considered file names also.. :-) If we rename the files, we will
> lose the history. anyway thats not a big issue. We know how to revert
> back if a problem arises.
No. We are using SVN, not CVS. Every history, including the renaming
operation, can be tracked down. So, just relax.
> [...]
> So, are you suggesting to continue with two names for the same project
> ? I would like to have a single project, single name and a single
> host.
No, I didn't mean to keep using two projects. I just suggested that we
can keep both mailing list running, archiving mails from each other.
Definitely we need to merge the two projects into one.
> [...]
>
> I too, I like the present name eeedit. what I tried to say is eeedit
> suits the project very best.
> atleast our plugin supports other editors upto some extent, if we
> concentrate on that issue.
> But lets not bother about those things for now. Lets make it perfect for vim.
All right.
> So, what shall we do ? All three of us want to stay here on GC.
> Sebastian claiming the following as the advantages with the sf. This
> message was sent to the guy.. martin.
>
> ---------------
> I never used google code. It looks nice, but I feel more comfortable
> with sf.net:
>
> 1) larger global user base
Yes, but 100MB is quite enough for us now.
> 2) shell access: e.g. hosting the update site is easier with shell
> access
It's not quite important.
> 3) free choice of homepage (static, wiki, etc: php and mysql
> enabled) (btw I'd like to rework that wiki soon ...)
Yes, that sounds wonderful. But I doubt that do we have enough time
maintaining that web site? It seems that we are all busy with our own
business and seldom have spare time working on this project. So I
don't think a free choice of homepage may help a lot.
> 4) administration fairly easy. (I could not find a document about
> features of google code ...)
That's true. I really appreciate the SF's administration features.
> But I think this is not a technical issue: The code is free and
> everyone can do with it what he likes.
>
> For me the most important thing is to keep people together. So I would
> suggest to stay here and reimport your work, rather than move to a new
> place, a new name etc. We have this list (40 members),
> http://vimplugin.org, a http://freshmeat.net entry etc. So I guess
> 'vimplugin' has quite a bit of infrastructure and popularity.
Well, it seems that we are "minority". OK, I just changed my decision.
I support moving our project.
> For me it seems also logical to stay here, because your work builds up
> on existing code. But that impression may be too subjective :-)
>
> Sebastian.
>
> PS I looked into the code last night. It works like a charm :-) What
> new features are there?
> ---------------
>
> lets discuss with them also. that will solve the problem.
Then should we arrange a online meeting? With IRC or MSN or something
else?
>
> --
> Best Regards,
> Nageshwar M.
>
>
Please remove the foot note.
>
>
Regards,
Edward L. Fox
Martin Krischik
> > 1) larger global user base
>
> Yes, but 100MB is quite enough for us now.
You missunderstood: It's about place 3 on google for "vim plugin
eclipse" vs (sorry to say) no where to be seen. Advertising is
important! From all the vim plugin's I have seen yours looks best -
but I found it last!
> > 2) shell access: e.g. hosting the update site is easier with shell
> > access
>
> It's not quite important.
>
> > 3) free choice of homepage (static, wiki, etc: php and mysql
> > enabled) (btw I'd like to rework that wiki soon ...)
>
> Yes, that sounds wonderful. But I doubt that do we have enough time
> maintaining that web site? It seems that we are all busy with our own
> business and seldom have spare time working on this project. So I
> don't think a free choice of homepage may help a lot.
I use PmWiki for all my SF projects - there is no time for anything
more complex. And nowadays I would use the build in SF-Wiki as well -
just to save the hassle of installing my own Wiki
> > For me the most important thing is to keep people together. So I would
> > suggest to stay here and reimport your work, rather than move to a new
> > place, a new name etc. We have this list (40 members),
> > http://vimplugin.org, ahttp://freshmeat.netentry etc. So I guess
> > 'vimplugin' has quite a bit of infrastructure and popularity.
>
> Well, it seems that we are "minority". OK, I just changed my decision.
> I support moving our project.
That tilted it for me as well.
> Then should we arrange a online meeting? With IRC or MSN or something
> else?
IRC would be fine.
Martin
Edward L. Fox
On 9/21/07, Martin Krischik <kris...@users.sourceforge.net> wrote:
> [...]
> You missunderstood: It's about place 3 on google for "vim plugin
> eclipse" vs (sorry to say) no where to be seen. Advertising is
> important! From all the vim plugin's I have seen yours looks best -
> but I found it last!
Sorry for my poor English... I know your point now.
> [...]
>
> I use PmWiki for all my SF projects - there is no time for anything
> more complex. And nowadays I would use the build in SF-Wiki as well -
> just to save the hassle of installing my own Wiki
OK, that's fine. The Google Code's built-in Wiki system really kills
me. I think another Wiki system may be wonderful.
> [...]
>
> IRC would be fine.
OK. My may-be-available time spans:
Mon Sept. 24, 0:00 ~ 15:00
Tue Sept. 25, 2:00 ~ 10:00
Wed Sept. 26, 0:00 ~ 4:00, 8:00 ~ 15:00
Thu Sept. 27, 5:00 ~ 15:00
Fri Sept. 28, 0:00 ~ 15:00
All in GMT.
>
> Martin
David Terei
Ok my late (lots of work lately, having to do overtime) reply to everyone's
emails on how to merge the two projects.
I think that we shouldn't do anything for the moment, except work from our
Google Code SVN base.
Since we are split on who's project to continue and who's to merge into the
other, let's just concentrate on the code for the moment. A month or two
from now once everyone has cut their teethes on the code a little we can
start up the discussion again.
I like this approach since it seems a little silly to merge at the moment
when we are not 100% sure that both groups agree on how to solve the problem
and who will be involved as well.
Also this is the quickest way to get started for everyone and in terms of
development infrastructure there is very little difference between SF and
Google Code the main argument between the two mainly involves end user
presentation and marketing (And like I said it would be temporary just for a
little while). The Vimplugin website could also be updated to tell users
what's happening or even post the releases to both GC and SF but that's
really up to the vimplugin guys.
So feedback is always welcome, I would hope everyone will be fairly happy
with this arrangement. If you want to start getting involved then also just
tell me and include your google account email and I'll happily grant you SVN
access.
Best Regards,
David Terei
Nageshwar M
by david is that Lets continue our work on the current eeedit code (
where ever we host the project in the future). Since it has more
capabilities and neatly structured. Is this decision is fine for
everyone ?
sorry, I didn't consider about the gvimplugin case.. if it has good
capabilities and provides scope for building advanced features, please
let us know.
As suggested by David, lets see for two or three months.. and based on
the activity we can solve the hosting problmes. These two months will
give everyone time to study the code and start working. And for these
two months temporarily, please work on the google code svn.
If these decisions are fine with vimplugin developers, just copy
everything including downloads from googlecode to sf and let the users
know whats happening. Mail your gmail addresses to david. He will
grant you the access to google svn. In case, if you have any
objections please mail back your points.
bastl
communications, especially from me. It's absolutely not good, but let
me first
give a bit background.
1.) I was working on a eclipse plugin for my job at the same time when
learning
vim. At that time a I had the first idea of an eclipse editor that
_is_ vim. I
registered the vimplugin at sf.net in 2005-11.
2.) No progress, other things to do.
3.) In the beginning of 2007, I found the tip how to embed a console-
vim into a
java program. I got my hands dirty again, and reached two milestones:
a)
embedding console-vim and b) porting the netbeans client/server
protocol to
eclipse (this one was hard). All this was so cool, that I revived the
project
and made some advertising (which worked obviously).
4.) I found that this was also on the agenda of Bram for the google
summer of
code. We had some contact, also with David and Nageshwar. But then ...
5.) I got completely distracted from this, due to a) my marriage
(think I was
on another planet from June 15 to July 31) and b) http://vim.wikia.com
. This
was very stupid, because I missed _everything_ what was going on here.
I was
absolutly not aware of this project, the svn-rep, or the mailing list
until
some days ago. I just got one or two mails that I ignored -- shame
over me.
OK, I finally found you and we are in contact again :-) This is anyhow
a good
starting point.
> > IRC would be fine.
>
> OK. My may-be-available time spans:
>
> Mon Sept. 24, 0:00 ~ 15:00
> Tue Sept. 25, 2:00 ~ 10:00
> Wed Sept. 26, 0:00 ~ 4:00, 8:00 ~ 15:00
> Thu Sept. 27, 5:00 ~ 15:00
> Fri Sept. 28, 0:00 ~ 15:00
I was on holiday last week, but I am _now_ on #eevp @ freenode.net. If
you read
this mail in the next few hours please join, so we can discuss
everything
online. I will check it every full hour. Perhaps we should arange
another
online appointment: Ill be online everyday next week from 8:00 to
17:00 GMT
roughly.
I repeat my main arguments:
a) the code is free
b) lets keep people together and join forces
c) sf.net is more flexible (perhaps /free/? GC doesnt 'feel' free)
d) also true: I started it, I love it ("my precioussss --
gollum" ;-) ).
Subsuming: d) holds also for david and nageshwar, but is worth nothing
due to
a). c) is technical and secondary. b) is most important
Best regards, Sebastian.
> > I use PmWiki for all my SF projects - there is no time for anything more
> > complex. And nowadays I would use the build in SF-Wiki as well - just to
> > save the hassle of installing my own Wiki
Just a sidenote: just discovered dokuwiki. That one rocks! It has all
features one
needs and it's so stupid simple and elegant! (after diving through a
lot of wikis
(twiki, mediawiki, pmwiki ...) I'm thinking about moving from pmwiki
to
dokuwiki for the homepage.but we can discuss that ...
bastl
bastl
---------------------------------------------------------------------
David Terei
- Move to SF.
- Use Trac.
- Use Google groups for mailing list and forums.
SF since yes it is more flexible.
Trac since I'm not a fan of the SF development tools (e.g. the bug tracker)
or its website.
Google groups since I think there much nicer and more powerful mailing lists
which also work well as a forum. Much nicer interface allowing developers
and users to post online which some prefer and its nicer for searching
archived posts/mail as well.
So basically we would use SF for SVN and web space. From the web site we
would clearly tell all users where to locate the forums and mailing lists so
as not to confuse them. Existing mailing list for vimplugin would be
maintained but people encouraged to move to the new mailing lists and we
would just post release announcements to it, with all development
discussions on the Google mailing lists.
While this does split things a little since we're not just using SF's tools
given the size of this project I can't see that being a problem at all. SF
allows you to disable features from memory so that the forums and mailing
lists and tracker would no longer appear.
Anyway, the best thing would probably be for all of us to chat on IRC some
time, or some other chat protocol everyone could decide on (MSN or Google
Talk is good for me). But perhaps hopefully you all think this is the
greatest idea since sliced bread and we can just agree over email :).
For Chat/IRC:
Mon - Fri: 0:00 - 14:00 GMT.
Sat - Sun: 0:00 - 9:00 GMT.
~ David
Edward L. Fox
On 10/2/07, David Terei <david...@gmail.com> wrote:
>
> Okay how about this:
>
> - Move to SF.
> - Use Trac.
> - Use Google groups for mailing list and forums.
>
> SF since yes it is more flexible.
>
> Trac since I'm not a fan of the SF development tools (e.g. the bug tracker)
> or its website.
OK, I like Trac very much! But I'm not quite clear about how to make
Trac work with SF's SVN service...
> Google groups since I think there much nicer and more powerful mailing lists
> which also work well as a forum. Much nicer interface allowing developers
> and users to post online which some prefer and its nicer for searching
> archived posts/mail as well.
>
> So basically we would use SF for SVN and web space. From the web site we
> would clearly tell all users where to locate the forums and mailing lists so
> as not to confuse them. Existing mailing list for vimplugin would be
> maintained but people encouraged to move to the new mailing lists and we
> would just post release announcements to it, with all development
> discussions on the Google mailing lists.
OK, please do this.
> While this does split things a little since we're not just using SF's tools
> given the size of this project I can't see that being a problem at all. SF
> allows you to disable features from memory so that the forums and mailing
> lists and tracker would no longer appear.
>
> Anyway, the best thing would probably be for all of us to chat on IRC some
> time, or some other chat protocol everyone could decide on (MSN or Google
> Talk is good for me). But perhaps hopefully you all think this is the
> greatest idea since sliced bread and we can just agree over email :).
>
> For Chat/IRC:
>
> Mon - Fri: 0:00 - 14:00 GMT.
> Sat - Sun: 0:00 - 9:00 GMT.
Well, your time spans intersect mine produce:
Mon - Fri: 7:00 - 14:00 GMT
Sat - Sun: N/A
The other members please make the intersection to these spans with
your own time spans and then we'll make the final schedule for our
online meeting.
>
> ~ David
>
>
> [...]
Nageshwar M
format. Tomorrow I have some important work.. so lets make it on
thursday.. timings are 9:00-14:00 GMT.
bastl
> Sorry, In the previous mail, I forgot to mention the time in GMT
> format. Tomorrow I have some important work.. so lets make it on
> thursday.. timings are 9:00-14:00 GMT.
I'm booked from 9-16 GMT on Thursday and Friday
Tomorrow would be fine for me, Thursday/Friday 8-9 GMT would be fine.
Next week would be generally ok from 8-16 GMT (with few exceptions).
My jabber adress is bastl at jabber.fsinf.de, my ICQ UIN 47128688.
Sebastian.
Edward L. Fox
On 10/3/07, bastl <dost...@googlemail.com> wrote:
>
> On 2 Okt., 18:51, "Nageshwar M" <whatisthi...@gmail.com> wrote:
> > Sorry, In the previous mail, I forgot to mention the time in GMT
> > format. Tomorrow I have some important work.. so lets make it on
> > thursday.. timings are 9:00-14:00 GMT.
>
> I'm booked from 9-16 GMT on Thursday and Friday
OK. So all the time spans intersection is:
Tomorrow "morning" 9:00 ~ 14:00 GMT.
>
> Tomorrow would be fine for me, Thursday/Friday 8-9 GMT would be fine.
> Next week would be generally ok from 8-16 GMT (with few exceptions).
>
> My jabber adress is bastl at jabber.fsinf.de, my ICQ UIN 47128688.
The only Jabber account I'm using is Gtalk. I have no ICQ account. I
think the best choice for all of us should be IRC. What's others'
opinion?
> Sebastian.
>
>
>
I hate the foot note.