Drupal 7 version of OG Mailinglist

Yes eventually. I have no immediate plans however as my development time on ogm is driven by my startup's needs (eduglu.com). I'm not planning on upgrading Eduglu to Drupal 7 for a number of months still so I won't be working much on upgrading ogm just yet either. That being said, if you'd like to help out, by all means do.

But if you (or others) are going to spend some time help helping out, I'd rather we finish pushing toward a 1.0 release on 6.x first - http://drupal.org/project/issues/search/og_mailinglist?text=&assigned=&s...

Also I'd be much more willing to move forward with a Drupal 7 release once Drupal.org moves to Git. Then it'd be much much simpler to keep the two versions in sync.

well the days are ticking down to the git move i understand - i have been watching this project for months and not yet had the stars align to give it a whirl - but now it looks like our first chance maybe on a D7 build - so if/when we get the go ahead we will see what we can do to help push your 6.1 out

Sub

I ran this through coder upgrade and attempted to fix as many things as I could manually.

Thanks Cliff! That's a great start! I've committed your patch to the Drupal 7 branch.

subscribing!

and gonna start using it with the patch. *crossing my fingers*

@Jaialin the 7.x branch is not at all tested and I'm 100% it won't work. If you're a coder and want to start cleaning up things, please do!

+1

Subscribing

Srsly looking forward to v.7 if that's gonna happen...

+1

Just wondering if anyone was working on cleaning up that D7 code at all? Not sure how I can help, but will be glad to any way I can. This module is critical my project and, at this point, I think it would be counterproductive to begin development on D6.

would it make sense to link 7.x branch on module's homepage? maybe this way someone would like to start working on it?...

Subscribing, However, your comment #8 scares me ;-)

I'm also in favor for a link to the d7 branch, some of us are not as git safely as you might wish. It took me a while to get the code. And maybe it would get things started even if there is a big "NOT WORKING" label on it.

I'm also interested in a D7 version.
For now I'm trying the mailcomment path. Does anyone know if the problems with mailcomment from D6 apply to D7 in the same way?

I have been talking with one other individual about helping to fund Kyle's work to convert this module to D7. It seems like there are probably a number of folks out there that want or need to see an upgraded version of this module, so I wanted to throw out the idea of putting together a Chip-In or something to that effect to get this knocked out. Feel free to contact me offline if you prefer, but it would be nice to see some solid commitments, even if they're small, from some of the people or organizations that have benefited or stand to benefit from this excellent piece of work that Kyle has put together.

Sorry if this is out of line in any way...I don't mean to step on any toes, but I need to see this work completed and I'm willing to contribute a good portion of the costs, so I'm hoping there are others in the same boat. Thanks.

I'd be interested in a new features overview.

My non-profit is interested in experimenting with Drupal (and other open source platforms) for very local online groups. We call them "electronic block clubs."

I'll chip in $250 today if five other groups step up in the next 48 hours.

We are tracking tools like VOIPDrupal, CityGroups (Drupal-based directory), and others.

We have a non-Drupal GPL platform - http://groupserver.org - that we use now for very public neighborhood forums. See: http://e-democracy.org We have no plans to stop using it, but we have an opportunity to test and compare other tech in the field with small private online groups for 100 households on down (or for an apartment complex).

Things that matter to us:
1. Full e-mail participation
2. Ability to require real names field with registration
3. Ability to moderate new users automatically, unmoderate selectively, or unmoderate universally
4. Ability to auto-insert poster name, selected profile info, and a link to their web profile into e-mail messages
5. Ability to limit the frequency of posting by a user by time to prevent domination and keep e-mail a viable option for more participants
6. Ability to create fully operational accounts with e-mail participation and group memberships select from the paper sign-up sheets we use - see http://e-democracy.org/inclusion

I will gladly donate $250 toward the cause if five others step forward to match me with no strings attached. Those are just some of my goals for online group technology that we've found crucial in our work.

On that note, I host a ~100 member online group with developers from many platforms interested in using open source tools to connect neighbors. One of my goals is to make local connecting work all over the place. Join us: http://forums.e-democracy.org/groups/neighborly

You'll note that I identified Drupal as a potential platform for our future BeNeighbors.org directory. It is not a done deal, but seeing momentum for multi-channel unified online group experiences in Drupal would be huge.

So who will join our pledge?

Steven Clift
E-Democracy.org

P.S. If you've played around with integrating DrupalVOIP, Organic Groups, and this add-on, let me know. My dream block club tool would allow people to have two priorities for delivery - normal and urgent. So if someone on the block has just collapsed in their yard, right after calling 911, someone could text, e-mail, or call-in and send a message immediately to the block asking for someone who knosw cpr to come to X location and it would go out to people how they prefer to receive it, while less urgent neighborly communication could be received normally. (Which may be an automatica call with text to speech for an elderly neighbor without Internet sharing some messages
via IVR.

I'm willing to join Steven and pitch in $250 as well if it means we get OGM development underway again - though the D7 port is lower on my priority list than some other features.

Thanks for pushing this David. Similarly Steven for throwing the first coins in the hat - I will chip in too. So with Tobias in, we have 4 of the 5.

But I suspect that the financial goal for achieving this is probably a factor of 10-50 larger than is being discussed and wonder how we can get some real figures for this - and commitments to fund it.

For CiviCRM we have successfully worked up a model for 'Make it Happen' projects - where the project gets properly scoped, usually involving some of the 'core team' which may be harder in the Drupal universe - then some core funders come along with the seed funding - and eg once a third or so of the target has been committed by the early adopters, then it gets made public, and pushed hard through networks to get the full funding.
The funding is actually 'paid' upfront, and returned if the project doesn't happen - or slid across to another project of the contributors choice.

Now I am not arguing for the above approach - just flagging a way of taking this process sufficiently seriously to get an outcome.

Also, i think that for a serious push to make this a goer for D7 will require some solid analysis of how robust an approach this actually is. I have supported (in spirit silently) Kyle taking this on since day 1 as it really seemed to be tackling some of the core limitations of other approaches - but that was 2 years ago maybe, and, well things change.

I am still hoping this is the awesome solution I think it is, but Tobias' comments, and looking at the D6 list, makes me wonder how proven it is for generic applications, without in anyway wanting to take anything away from Kyle's huge efforts on this (still love you kyle)

Count me in for $250 as well.

Kyle, do you have a Paypal account where we can send the money?

Shai

Super all. Since 48 hours starting Friday isn't the best time to start a challenge.

Let's see what we can all do in one week.

Also, if needed/desired, my U.S. registered non-profit can take donations which will dedicate 100% to Kyle's work per this topic as it benefits many non-profits and our org's mission. This would make contributions tax deductible at least in the U.S. and other countries only depending upon local laws.

I'm really glad to see all of the encouraging responses. It's interesting to see you pop up on here, Steven, as I've been following e-democracy's efforts for a while. I appreciate you extending the challenge, as the weekend was sort of rough timing. Also, running the funding through your organization sounds like it may be a solid option, particularly for the individual donors.

Like you, Pete, Kyle's approach has always seemed to address some of the inherent limitations of other means of achieving similar functionality within Drupal. I would, however, also like to see some scoping and analysis, if possible, to see if there are opportunities to improve the approach during the conversion.

By the way, you can chalk me up for $500. We'll see how far we get next week...this is very encouraging. Have a great weekend everyone.

I was going to say in my first post - match your $250 and raise to $500 - but wasn't sure how it would go down - anyhow - match your $500 ;-)

The company I'm working for is also willing to spend some money to make it work. But I talked to them and they would need to know what can be accomplished for a chip in and how long it would take. They are willing to put in $250 maybe even $500.

Hey everyone,

It's been really gratifying to see the continued strong interested in OG Mailinglist! Sometimes with open source code you only hear complaints so you start to wander if anyone actually cares :)

So now that we have the pledged money, the next question I suppose is what to do with it. I'd say the highest priority is to get OGM ported to Drupal 7 to ensure its continued viability. Beyond that, people have suggested there's some feature improvements / bug fixes that need done? For those that have taken a close look at OGM, what's your top priorities there? Creating or linking to existing issues would be helpful. Netclift already did this but it'd be nice to hear other's thoughts.

I'm also interested in hearing about specific ways to approve OGM's general approach to solving the email integration problem. Several of you made mention of that.

Hi everyone,

Glad to see this activity and to see development of OGM ramping up again. A brain dump of thoughts from my end:

1) I approve of the idea that we all donate to Steven Clift's charity and run this through that channel, and am happy to go along with it. I also think we could try to do a kickstarter thing if more money is needed to which our various stakeholders can contribute.

2) The port to D7 in and of itself is not an immediate priority for kabissa, though I can imagine that later in 2012 or 2013 kabissa.org might be upgraded. I also understand that this increases interest. But I would like backward compatibility to be prioritized as much as possible.

3) More important for me are usability features both online within organic groups and in email. I am not interested personally in "abstracting" OGM in any way so that it can be used on a non-OG site, but for improving OGM so that it essentially replicates Mailman's robust email features with the benefits of organic groups.

For #3, features I am looking for include things like this:
- improved presentation of discussion threads on the site including full support of file attachments
- MBOX import/export features to allow moving discussion archives to other platforms.
- CSV import/export features to allow migration of group members to/from other platforms
- improved membership lists/member directory for exploring and contacting fellow group members, seeing what they are posting, when logged in last etc
- improved membership management tools for group owners for inviting/adding/removing members
- improved error reporting and handling when e.g. email is bounced because of bad from address

4) davidspencer mentioned scoping and analysis - there is an opportunity via kabissa to do a consultation of our members, many working in Africa where we believe email lists have still a crucial role to play, to determine whether OGM is actually needed and if so what improvements might make it most useful. Now that there is an opportunity to actually move forward on features, we could go ahead with this consultation, which you are welcome to also join: http://www.kabissa.org/steering-committee-moving-forward-kabissa-email-d...

5) We have currently turned off groups for public use pending this consultation and are only using it internally, which works 'a peine' but does have bugs we have to work around. I can update the relevant issues in the OGM tracker if Kyle is going to work on fixing them. Main ones include improper/inconsistent handling of file attachments, confusing error reporting in bounced emails, random and bizarre occurrence of new node upon reply by email.

6) and a final thought - is anyone willing to be a co-maintainer of OGM/is Kyle willing to have a co-maintainer? Like all developers he gets busy sometimes and it would be more sustainable to have more developers take responsibility for the code.

Cheers,

Tobias

Oh, and I just got an email from GOOD about a $2500 prize that we could be in the running for: http://jumo-organizations.maker.good.is/

Just chiming in to say I can bring another chunk or two of funding. I haven't managed to do an install, so can't speak to feature work. A D7 install would be most welcome (we're planning a new site), but so would further refinement as per #28.

I might be able to chip in for this as well (but not as much as the other contributions — I need it for a pro bono site so it would be out of my own pocket) if a D7 port is at the top of the list. This functionality would be welcome!

Changing the title so this makes more sense on our dashboards.

I went off and got busy! I can set up a dedicated place to aggregate funding.

Could someone whip up a Google spreadsheet where we can track pledges, contact information, and which ones want to go through my E-Democracy.org non-profit and if any want to pay Kyle directly?

To keep this simple, if anyone wants a funded feature other than a Drupal 7 version, they need to make that clear on the pledge spreadsheet.

We need Kyle to estimate the number of hours for a Drupal 7 effort and what his special hourly rate is for this effort. If pledges go far enough, then we will know how big the pool is for other features (or the deficit to get Drupal 7 done).

Sound good?

Will see if i can get the google doc going in next couple of days if no one else has - am on the road but will have 3 days in brussels so may get a window to do it.
Not quite clear what you meant by "I went off and got busy!" but suspect you mean - you got distracted from pushing this due to other demands - rather than 'you got busy getting this moving' ;-) But happy to be told i am wrong.

Hi everyone,

I've created a quick and dirty spreadsheet at http://bit.ly/IqYQ8s - please add your name, d.o username, amount pledged and any comments to that spreadsheet. This is specifically for the d7 port - if we get traction for that then we can do another round of fundraising for features. What say?

Cheers,

Tobias

From what I can see the pledge has gotten a decent amount of cash. Is there still a big money gap to realize this? Do you have an idea when work could be started and how long it would take given the constraints of the people involved in development?

We really appreciate Kyle's work and are chipping in on the Google doc. Is there a final estimate or timeframe? and what would the shortfall be, if any? Thanks so much.

Actually, based on my preliminary discussions with Kyle (and considering some contributors that haven't added their names to the spreadsheet yet), I think we're actually pretty close, at least to a basic conversion. If we start talking about building in much in the way of new functionality, of course all bets are off, but specific functionality should really be the responsibility of the party requesting it. Just running the module through the latest version of the coder process at http://upgrade.boombatower.com/ will probably get us a pretty good ways down the road, if someone wants to take that on.

david, if I understand correctly we are pretty close to being able to finance the drupal 7 module with the same functionality as the 6 module, right? I agree with the point of extra functionality having to be financed separately. Is there an estimate about the time required to create a working 7 version? And if Kyle could start with this soon?

Hey guys, I've been talking about this to David behind the scenes but to add it here as well. I think enough money has been raised to port the module to Drupal 7. If the port ends up taking longer, I'll just donate the remaining time. I think running the code through upgrade.boomtower.com is well worth the $25 cost from the amount of coding / research time it'll save.

Kyle and all. Sounds good. Where do we send the check to fulfil the pledge and to whom should we make it out?

Great. For those who want to be part of the non-profit related contribution, I've offered to collect contributions.

I want someone to be the agreed person that says "The works is done. Pay Kyle." Tobias? Then I'll set up an online option for donations. I'll eat the transaction cost in addition to the $250 I pledged from my org for the convenience of just doing this electronically.

OK?

Steven Clift
E-Democracy.org

This sounds really great, post here as soon as the work can be tested and when the pledge has to be fulfilled. Thanks guys.

Steven,
Do you have the system in place yet so people can fund their contributions to the project? Kyle has said he can start the work fairly soon, but I don't want to leave him hanging. Nor do I want to lose any of the fantastic momentum we have on this project.

I also have access to an unusually low transaction fee gateway (via a contract with a distributor), and could set up a channel if something goes awry with the discussed plans.

We may have to take you up on that offer, @LP. I haven't had any luck with trying to track Steven down and we need to get all of the funding in place. There are other options, but if you have something in place already, that would be preferable. Let me know if you need any assistance.

I am right here ... the format of these digests make it difficult to track.

My last query was all I need is:

I want someone to be the agreed person that says "The works is done. Pay Kyle." Tobias? Then I'll set up an online option for donations. I'll eat the transaction cost in addition to the $250 I pledged from my org for the convenience of just doing this electronically.

So, David is that you??

Steve

P.S. http://stevenclift.com/contact - Reach me all over

Here's a patch that gets install/uninstall working for the 7.x branch.

Thanks, Steven. I can, for the sake of getting everything everything rolling, take responsibility for that role, but I think it would be beneficial if someone with some stronger coding chops was involved as well. Anyone?

Let's go ahead get the donation mechanism in place. Kyle is ready to work on this. Will you post the link here or contact the project contributors directly?

I appreciate you help.

David

.

Donate away!

http://givemn.razoo.com/story/Drupal-7-Version-Of-Og-Mailinglist

Again, as this matches our non-profit mission to promote best practices in online community engagement - that of accessible e-mail access, donations to this campaign are tax deductible in the United States. They may be tax deductible in other countries, but you will have to check your local tax laws.

Thanks David!

Mine's in - come on guys

And i updated the spreadsheet with 'status' so we can mark ourselves off

Hi everyone -

Thanks Peter for reminding me of this thread - not sure why but I don't get notified of updates by email.

My question about backward compatibility hasn't been answered - see #28 above. I am happy to contribute to this if it generates interest in OGM and helps drive development forward, but also only if the new development is backward compatible with D6. I don't know yet when Kabissa will be upgraded to D7.

Answer me that and I'll throw my $250 into this D7 upgrade - and look forward to investing more in making necessary improvements.

Cheers,

Tobias

@tobias you have to change your notification settings on your Drupal.org account. Profile -> Notifications. Then change OG Mailinglist to send you emails for issues you follow.

Thanks @sethfisher! I have this sorted out now.

@Tobias I don't see any need to change the data model OG Mailinglist uses and if there is any changes, there'll be an upgrade method written so need to worry about BC-breaks.

I just donated the pledged $250 on behalf of Kabissa and updated the spreadsheet.

Who's next?

Donate: http://givemn.razoo.com/story/Drupal-7-Version-Of-Og-Mailinglist
Pledge spreadsheet: http://bit.ly/IqYQ8s

Cheers,

Tobias

Kyle, is this http://drupalcode.org/project/og_mailinglist.git/log/refs/heads/7.x-1.x the latest 7.x branch code or have you done some work offline? Just wondering, I have a itch to scratch and I would dive right into the code.

My $500 contribution to the project has just been added to the spreadsheet. We're up to $1250 in actual project funding, so who's next? Let's get this effort completely funded.

Thanks,
David

that's great, thanks David for also pitching in.

Kyle, we'd all like an update on the next steps. Thanks! :)

@mahfiaz I'm not really sure about the status of that branch. Another programmer took a crack at porting the code to Drupal 7.x. but never did get it working. I haven't looked at what he did in quite some time and am not really sure about its quality. You might want to fork from the latest 6.x code as there's been quite a few commits since the 7.x branch was split off.

@tobias. About timing. Looking at my schedule, the next big free chunk of free time I'll have is June 18 + 19. I'm planning on spending a good bit of time on those two days doing the port. If anyone wants to jump in before then, feel free.

@mahfiaz I took the 7.x branch and got it working for install/uninstall; that's the patch is #48. However, that 7.x branch was last touched in March 2011...so it's probably best to take Kyle's suggestion and work off of the latest 6.x branch to port. I wish I had thought of that myself, what I did is basically a waste.

We are up to $1750 in the bucket ($1500 donate plus my org's $250).

Looking at the spreadsheet - http://bit.ly/IqYQ8s - I see $1000 in pledges still out there. One has some feature conditions.

If you are planning to pay Kyle directly for some reason, let us know.

If someone can help contact the remaining pledgers, that would be good.

Also, now might be a good time to post the donation opportunity in a new topic that others might notice or other places appropriate on Drupal. Go for it!

I did some work on the upgrade. Instead of starting over I merged all the changes which were done on master branch back in, so although I started with the old 7.x branch, it's now again up to date compared to 6.x version.
It should be half the way there. Quite a number of things seem to show up and even work, but I haven't got to actually sending/receiving any emails yet.

If you are interested or plan to work on it as well, please pull the code from github:
https://github.com/mahfiaz/og_mailinglist_7/tree/7.x-1.x

One thing which would be very helpful is string review. If someone could find all the strings which are enclosed between t('This is a translatable string.'), and fix mistakes. Fixing comments' grammar has slightly lower priority.

Other things to do:
I added descriptions to the database tables. This would need an database upgrade function (or we could remove the descriptions again).
Make sure that actually sending and receiving emails works.
Make sure that upgrading from d6 works.
Consider, if it's worth making group's email prefix an regular field handled by Fields API.
Probably more :)

Gang,

I upped my pledge to $300 and paid it.

For those hunting around for the relevant URLs, I'll repeat them here (Kyle, add them to the project page).

Donate: http://givemn.razoo.com/story/Drupal-7-Version-Of-Og-Mailinglist
Pledge spreadsheet: http://bit.ly/IqYQ8s

Shai

Kyle - any update on this? Anything we can do to help?

I just want to let everyone know that according to our online donation system we have $2050 ready to be spent on Kyle's effort. I am relying on those in the know to tell me when to cut a check for completed work.

Just added another $500 to the pot. Git R Done!

I'll put in another $500 if it's usable in production by 7/31 or 8/1 :)

I did some work on it and now it is as following:
* Group email is held in a special field, og_mailinglist table was removed (it held only group email prefixes).
* Installation works good.
* Sending emails should work, at least it gives no errors.
* Wandering around in drupal gives no errors.
* Admin pages look good.
* A lot of code cleanup.
* probably more, for complete list of changes take a look at commit log :)

To do:
* Recieving emails is totally untouched and doesn't work.
* Digest emails need refactoring.
* Everything needs testing.
* Upgrade path needs to be written. If you have an up-to-date OGM installation which could be used to test upgrade path, then please speak up.

To test it or work on it, please checkout the code and give it a try. Use OG version 7.x-2.0-beta1.
http://drupal.org/project/og_mailinglist/git-instructions

At first I used the stable OG 1.4, but that version had group ids + group node ids. It was hard to tell by variable and function names which one was which. Also it caused more database calls. As far as I could tell, OG 2.0 is going in the same direction as the rest of drupal by using fields, entities and stuff, so I upgraded. But since OG has removed og table from the database, there are many database calls which need to be rewritten.

I will be away at a children's camp from now until the 5th of August, at that time I am unable to work on it. I would be delighted to find it ready by then :). Kyle? If anybody creates patches then I would happily commit these later, just make sure you make some noise so the work will not be duplicated.

As for tclnj's offer, I am unable to take this challenge. I think that one person who is somewhat familiar with OG stuff might be able to get it working in five days (if working full-time), but not production ready, testing takes time.

"not production ready, testing takes time"

I know, hence the "usable in production" - if just barely - and not "production-ready" request - hiccups expected :)

Some more updates. In addition the great fixes mahfiaz has been making, I tracked down a number of bugs around sending emails from new nodes/comments so both of those work correctly now with Mailgun (and presumably other sending methods though I didn't test any).

I tested receiving emails and there's an SQL error in og_mailinglist_transport.php that I didn't have enough time to track down.

Getting closer...

Extending additional $500 motivation to 8/15. Need fully-functional beta for D7 by 8/15... not perfect, but functional.

Have mailgun account already configured for this, if that helps :)

Standing by :)

A small update on this issue. I fixed errors in og_mailinglist_transport.inc (which was where Kyle last stopped). Although there are a lot of TODO marks in that file, now recieving emails gave me no errors on two tests and content was successfully published both as new thread (node) and comments.

I won't be working on this for a week, so everybody is welcome to do so yourself :)

Also, I think brave ones could now test it on new Drupal 7 installations (no upgrade path yet) and post all errors to the issue queue.

Sounds good... will look at testing this if I can as I am keen to use it. (Might be time to publish a 7.x dev branch on the module page perhaps?)

babbage, that's awesome. Just let us know how it worked or failed for you :)
As for publishing, I don't think it's that ready yet. Quick search revealed that og_mailinglist_digest_email.inc contains 4 db queries which refer to nonexisting db table og and 1 to now gone og_mailinglist. But I can't fix these right now.

In order to test this, I needed to update and apply the patch in this issue: #957994-2: og_malinglist_utilities needs to search the standard php include path in mimeDecode_load_library(). Just in case anyone else has need of this.

Trying to test this. Having some success with it, but not complete. My testing is complicated by the fact that I didn't have a Drupal 6 version of this module installed on my server, so I've been needing to set up the initial exim integration also, not just install and test the module.

I've had some difficulty with that. The module's exim instructions assume the split configuration approach for exim, whereas the VPS I'm installing this on has a single non-split exim.conf file as it is running DirectAdmin. I've therefore been needing to manually insert the router and transport into the configuration. I've successfully got incoming emails creating nodes and being sent out to group members, under the following conditions:

• If I set the email to be routed to the og_mailinglist transport early in the order, and do not set the "unseen" flag on the router, then both messages to the group and all other mail to the server is lost, undelivered and without an error message returned to the sender.

• If I set the email to be routed to the og_mailinglist transport early in the order, and set the "unseen" flag on the router, then messages to the group are sent out to the group, and all other mail is delivered. However, the sender of the message to the group also receives a permanent mail error, "Mail delivery failed: returning message to sender", even though it has correctly been sent out. (Edit: This actually makes sense to me that this message is sent out when "unseen" is set; what I don't understand is why the first setup described is causing the loss of all email... I would have thought the first setup is the correct one.)

• If I set the email to be routed to the og_mailinglist transport last, ie. only if it has not been delivered or rejected by any other mechanism, then the messages are never sent to the group.

The other pertinent issue is that while nodes created on the website are sent out to the group by email correctly prefixed with [group-name], when they come in by email they are prefixed by the exact string "[Array]". Unsure if this is related to the above.

I realise this sounds more like a support request than regarding this issue, and it does seem to me that it is highly likely that this is not specific to the Drupal 7 code but rather reflects an exim configuration issue. But any suggestions appreciated so I can continue testing the port!

I'm very sorry that I have not added my pledge but my client rolled back on me, and he does not want the work to be done. So I will not be possible to donate. Sorry again, it took a while to get his decision. I wish you good luck with the work, and hopefully I may be able to do fulfill my pledge at a later time. Thank you anyway.

babbage, I fixed the [Array] in title issue. It was my mistake.
Unfortunately I cannot help you with exim problems. I am pretty much in the same place as you, I have never configured an email server and my current OGM installation is the first one.

reptilex, no problem, thanks for letting us know anyway.

How far along are we toward completing this project? Let me know when to release the funds for adequately completed work.

I also want to know how this is going. Kyle?

Let's correctly set this against the 7.x-1.x-dev branch. I've got this installed on a development site and am testing it. If it was urgent for you to implement this, I'd say in some cases you could deploy this right now. There are a few bugs I'll be posting issues about still—it inserts the entire [listname@domain.org] as the start of the email subject, rather than just [listname] and doesn't handle re-writing the subject line correctly when you reply to a message, so you get a subject like [listname@domain.org] Re: [listname@domain.org] Subject line. I'm also seeing problems with the rendering of attached thread history when a reply to a previous message is sent out... the reply looks fine, but at least in my HTML emails the thread history looks like a plain text encoding of a MIME enclosure.

That said, these are both bugs you could live with if deploying was more important that perfect. The other bugs that were more significant we seem to have identified and fixed. This is certainly close to being able to be fully certified as production ready, in my opinion.

Edit: Oh, and all replies go to the list, regardless of whether you've set the reply-to header option in the preferences for the list or not.

Further edit: The patch in #1778634: Comment published status check looks for wrong value in database fixes the subject line errors listed above, and also fixes a previously unrecognized error with incorrectly checking for whether comments on a previous message were open or closed.

A status update. Everything looks better now, the todo list is down to:
* further testing and
* #1706858: Add upgrade function to remove old/unused tables.

All things which babbage notes in the previous comment, are fixed.

So now I really encourage you to go ahead and try it out on a new D7 installation.

great to hear - can it pls be wrapped up as a 7.x dev release? I think more testing is likely to occur once it is obviously available, rather than just to those of us following this thread

Aaaand it's done :)

okay - now we are cooking with gas - thanks

Great work mahfiaz!

Now the upgrade path works for me. If it doesn't for you, just file a bug report.

If you happened to install it on D7 some time ago and already use it, then you might need to update schema_version for og_mailinglist by hand, see: http://drupal.org/node/1706858#comment-6499440

babbage, have you worked out the exim stuff? Could you write a how to for other single-configuration file users?

My autogenerated /var/lib/exim4/config.autogenerated configuration file has the following right between local_user and mail4root sections:

drupal_og_mailinglist:
  driver = accept
  transport = drupal_og_mailinglist

Anything I can do to encourage others to start testing - at least the others who contributed ;-)

hey, this is awesome news. great work, everyone! :) I'll put it on my todo list to attempt an upgrade to d7 and do some testing.

-t

I would like to once more encourage everybody to test the module. Now emailing attachments Works For Me™ (except handling attachments errors, see #1801786: Mailed attachments error reporting to let me know how you would like it to work).
Also threads belonging to several groups at once work pretty good.

hey mattias - thanks for the updates - can you clarify what the expected outcome is for 'threads belonging to several groups'.

So there is a node that is published to several OGs - it goes out to members of all those OGs.

Some of those members are members of more than one of these OGs.

They reply to the email. The comment gets added as a comment on the node - and is visible only on the groups they are in - or on all groups

i don't understand how OG handles this anyhow ie if a comment is posted to a node on several groups, does the comment show wherever the node shows (i would expect so) or only on those ogs that the commenter is a member of?

petednz, it will be visible on all groups. There will be only one node and only one list of comments, so yes, the comment will show wherever the node shows.

Howdy all, I just wanted to let people know we are sitting on the pile of money and are ready to write a check(s) to the right people when told that this funded work is satisfactorily completed. Is it complete?

I get the impression that mahfiaz did a bunch of this work, but I need to be told by davidspencer and tobias at least who to pay what and when.

Thanks,
Steve

P.S. Where is the 7.X version in action?

Steve - thanks for poking on this.

What I am saying below is not specifically related to paying anyone for anything. As one of the funders I am still delighted that this project has progressed.

Back in Sept I sunk a bunch of time in to testing with mahfiaz' support but needed to finish that by producing a spreadsheet of things we know don't work, and extras that we think should work.

I then got sucked in to a bunch of other projects and haven't been able to come back to it.

It needs more testing - especially by those who also helped fund this - IMO.

As Mahfiaz did most of the upgrade work, I'd be more than comfortable giving him all the money -- if he wants to share it with some of the more active testers / bug reporters, that'd be fine with me too.

Mahfiaz, how far are we from a stable non-beta release?

Is there anyone who contributed who has any remaining 'I didn't get what I was reasonably expecting" concerns?

If no concerns are raised, I'll pay Mahfiaz upon receipt of an invoice.

One thing I would like to see is a demo verision in operation so more people like me who are not developers can kick the tires and then decide if we want further hire folks to install and customize it for us.

I want to explore possible connection with VOIPDrupal and add sms/voice options to the online group miz for example.

Steve

Hi Guys,

Just checking in on this to see how "stable" the dev version is at present and/or when a stable might be available?

Thanks.

I received one query from one of donors suggesting they didn't have what they needed.

Obviously, most appear happy, or I would have received similar such queries.

So let me repost:

Mahfiaz, how far are we from a stable non-beta release?

Is there anyone who contributed who has any remaining 'I didn't get what I was reasonably expecting" concerns?

If no concerns are raised, I'll pay Mahfiaz upon receipt of an invoice.

One thing I would like to see is a demo verision in operation so more people like me who are not developers can kick the tires and then decide if we want further hire folks to install and customize it for us.

I want to explore possible connection with VOIPDrupal and add sms/voice options to the online group miz for example.

Steve

I really want to see the money we put in paid over. Mahfiaz has done a huge bunch of work on this.

Yes, I'd love to pay. I just need an invoice!

Yeah, Mahfiaz has done a superb job. Let's get him the money.

Amen to that. This donor is happy.

Can someone please summarize and/or update the issue summary? I don't get the picture what's the state of the module right now. TIA!

Axel:
Many are using the module in D7 albeit some features are limited/missing.

Things I would like to improve before releasing any alpha is attachment handling. I already have fixed it once, but I accidentally did git reset --hard in that directory and that accident has discouraged me for months. That said, I hope to start working on it before February. You will know there is progress, if commit count is growing.

As for using dev version, it has seen a few regressions in last September and October, but these were reported and fixed pretty soon. My site has been running on ogm since last July IIRC, so I don't see any reason why one couldn't use it if it meets your needs.

I think you should release an alpha. Alpha doesn't mean things are feature complete. Betas are generally used for that. Releasing an alpha just gives people a stable point to develop with and file bug reports. Dev versions are a pain to deploy because you never know exactly what you're getting as every commit push triggers a new dev version. I'd release an alpha version now and continue to release new ones as you fix bugs or make other changes. Then once the attachment handling work is done and stable, release a beta.

Here you are, 7.x-1.1-alpha1 has been generated. Yay!

Yay! :D

Yay yay

Hi - about to try D7, getting a message here http://pear.php.net/package/Net_Curl/redirected

"This package is not maintained anymore and has been superseded. Use HTTP_Request2 instead."

Will this work on HTTP_Request2?

Thanks

MickC, I will shortly update OGM to support both Net_Curl and HTTP_Request2. But it is highly likely that you won't need them at all. Turns out that the installation instructions have fallen behind. See this: https://drupal.org/node/2178079

What would it take to get this module out as Beta?