Date   

locked moderator "claiming" a post to work on

 

Mark, or anyone,

What's the status/functionality of the "moderator claim pending post" feature? I just had a moderator in my test group approve a post that had  already been marked as "claimed" by another moderator. She had no idea what "claimed by" meant (I hadn't yet mentioned this to anyone) and just went ahead and edited and approved the post with no problem. Meanwhile, the first moderator had "started" on the post but then just left it alone (and had no idea that her starting on it would result in its being marked as "claimed" by her).

So my questions are:

(1) What actions by a moderator on a post result in it being marked "claimed" by them;

(2) Once it's marked as claimed, can it be "unclaimed" if the mod decides not to deal with it; and

(3) Is a "claimed" post unavailable for moderation by another mod, or does the "claim" just provide notice that another mod has the post rather than prevent any other mod from working on it?

Thanks.

J


locked Re: Early 2016 Roadmap

Duane
 

- Decide whether beta@ should be renamed, and if so, to what.

I think that to some extent, this group is still for beta items - suggestions, changes, feedback - although I wouldn't be against a name change as suggested to dev@ or similar.

- Figure out if there's anything I can or should be doing to funnel people to GroupManagersForum@ and similar groups, both to reduce traffic on beta@ and to keep its' scope more focused on development/improvement of the service.

I'd like to see more folks use the GMF@ for "normal" questions and reserve this one more for feedback, concerns, and discussion of new features.

I know it's the least favorite part of any developers work, but until there's better documentation, I suspect there will be questions about "simple" things that already exist or are planned. Especially when they work a bit differently than Yahoo and are in a state of flux. Those should really be addressed at GMF@ or similar. I believe that Shal is moderating GMF@ by himself, so if traffic picks up, he may add a moderator or two.

I hope you (Mark) got to enjoy your time off - now back to the salt mines! ;>)

Duane


locked Site updates #changelog

 

Changes to the over the past couple weeks:

  • CHANGE: Ignoring LinkedIn invite spam sent to +subscribe addresses.
  • BUGFIX: Fix for broken encoded subjects.
  • BUGFIX: Auto orienting cover photos now.
  • BUGFIX: For messages without References, that we match to a thread using the subject line, we weren't checking to see if the thread was closed.
  • BUGFIX: Group messages and threads are formatted better on phones.
  • BUGFIX: When paginating through the activity log, the filter selector would be reset.
  • BUGFIX: In the Files section, the edit/move/delete icons were always displayed, even when they weren't available.
  • NEW: For not confirmed members, there's now a button on the member subscription page to send them another confirmation email.

Cheers, Mark


locked Re: Early 2016 Roadmap

 

On 4 Jan 2016 at 10:34, Mark Fletcher wrote:

- Complete the database feature.
- Complete the long in-progress subdomains feature.
- Figure out what the Enterprise plan will be, if there is one.
These are the top issues for me also. I would like to have other premium
options other than $10/mo, maybe a la carte - like extra storage,
integrations, skins, no ads? I would also like to pay something to support
groups.io just for using the basic service, but not $120/yr.


- Decide whether beta@ should be renamed, and if so, to what.
Yeah, I guess beta@ should be renamed. Something short, like dev@?
Something to reflect the group purpose of development of the service.


- Figure out if there's anything I can or should be doing to funnel
people to GroupManagersForum@ and similar groups
Can you put a link to the groups in the Help Center?


(Here I'm using the @ sign after a word to designate a group name.
I like it. Beats the alternative of adding "groups.io" after every group
address.


--
Jim
Poston@vch-nv.us

<< GUI:A set of pretty pictures to entertain the illiterate. >>


locked Re: Early 2016 Roadmap

vickie <vickie_00@...>
 

Hi Mark,

Welcome back.
Hope your vacation was memorable. Happy New Year to you also.

In my opinion I feel Moderators should be funneled to managers group. io   with 
  help questions about groups . 

While the beta group should be about  group  improvements and  development request.

And your email should be about just that Developer@....

Talk is a lot of Yahoo groups are looking into  creating groups with  group .io  especially
with the  news  that Yahoo is looking to sell  the core of their business  or possibly the
internet business. 
Which means these moderators will need a place to ask  questions on how  to manage
their groups..   I feel   newbie moderators and  expert moderators  should be redirected to Shal with  group administrative/  manager questions.

Thanks for reading my suggestion


Vickie

 









From: Mark Fletcher <markf@corp.groups.io>
To: beta@groups.io
Sent: Monday, January 4, 2016 1:34 PM
Subject: [beta] Early 2016 Roadmap

Hi all,

I hope you all had a good New Year! While I did monitor beta@ during my vacation, it will take me a few days to go through and respond to the various threads from the past couple weeks. I appreciate your patience.

I've been thinking about what I'd like to get accomplished in the first part of this year. Here are my thoughts. Groups.io has been in quasi-beta status since launch (quasi because I haven't really made a big deal about it). I'd like to officially move out of beta status. To get there, I'd like to complete the following:

- Complete the database feature.
- Complete the long in-progress subdomains feature.
- Figure out what the Enterprise plan will be, if there is one.
- Work on some of the issues discussed over the past two weeks, including invite and join flows, and permissions.
- Bugfixes, of course.
- Decide whether beta@ should be renamed, and if so, to what.
- Figure out if there's anything I can or should be doing to funnel people to GroupManagersForum@ and similar groups, both to reduce traffic on beta@ and to keep its' scope more focused on development/improvement of the service.

Moving out of beta status will not have any real effect on the service. I will continue development in the same manner as now. Like all software development, there will still be bugs. It's more to say that we've been around over a year now, lots of people use the service, and things (generally :-) ) work.

Anyways, that's what I'm thinking. Let me know if you have questions or suggestions, especially about the last two bullet points.

Thanks,
Mark
(Here I'm using the @ sign after a word to designate a group name. Annoying? Useful? Meh?)




locked Re: Early 2016 Roadmap

Rajmund <brajmund2000@...>
 

Hello Mark,
I like the idea of the beta group, in my opinion, it should remain. Allows listers to gain ideas, to give feedback, and in a way, to help you out. ?Anks  a great, and reliable group host!



Sent from an iPad

On 4 Jan 2016, at 6:34 pm, Mark Fletcher <markf@corp.groups.io> wrote:

Hi all,

I hope you all had a good New Year! While I did monitor beta@ during my vacation, it will take me a few days to go through and respond to the various threads from the past couple weeks. I appreciate your patience.

I've been thinking about what I'd like to get accomplished in the first part of this year. Here are my thoughts. Groups.io has been in quasi-beta status since launch (quasi because I haven't really made a big deal about it). I'd like to officially move out of beta status. To get there, I'd like to complete the following:

- Complete the database feature.
- Complete the long in-progress subdomains feature.
- Figure out what the Enterprise plan will be, if there is one.
- Work on some of the issues discussed over the past two weeks, including invite and join flows, and permissions.
- Bugfixes, of course.
- Decide whether beta@ should be renamed, and if so, to what.
- Figure out if there's anything I can or should be doing to funnel people to GroupManagersForum@ and similar groups, both to reduce traffic on beta@ and to keep its' scope more focused on development/improvement of the service.

Moving out of beta status will not have any real effect on the service. I will continue development in the same manner as now. Like all software development, there will still be bugs. It's more to say that we've been around over a year now, lots of people use the service, and things (generally :-) ) work.

Anyways, that's what I'm thinking. Let me know if you have questions or suggestions, especially about the last two bullet points.

Thanks,
Mark
(Here I'm using the @ sign after a word to designate a group name. Annoying? Useful? Meh?)


locked Re: Early 2016 Roadmap

 

Will GMF continue to be moderated? I prefer beta for that reason.

Sent from my iPhone

On Jan 4, 2016, at 10:52 AM, Steph <hsrsp@...> wrote:

How about keeping this one as beta@ and have a sub group called GroupManagers@

Sent: Monday, January 04, 2016 12:34 PM
Subject: [beta] Early 2016 Roadmap

Hi all,

I hope you all had a good New Year! While I did monitor beta@ during my vacation, it will take me a few days to go through and respond to the various threads from the past couple weeks. I appreciate your patience.

I've been thinking about what I'd like to get accomplished in the first part of this year. Here are my thoughts. Groups.io has been in quasi-beta status since launch (quasi because I haven't really made a big deal about it). I'd like to officially move out of beta status. To get there, I'd like to complete the following:

- Complete the database feature.
- Complete the long in-progress subdomains feature.
- Figure out what the Enterprise plan will be, if there is one.
- Work on some of the issues discussed over the past two weeks, including invite and join flows, and permissions.
- Bugfixes, of course.
- Decide whether beta@ should be renamed, and if so, to what.
- Figure out if there's anything I can or should be doing to funnel people to GroupManagersForum@ and similar groups, both to reduce traffic on beta@ and to keep its' scope more focused on development/improvement of the service.

Moving out of beta status will not have any real effect on the service. I will continue development in the same manner as now. Like all software development, there will still be bugs. It's more to say that we've been around over a year now, lots of people use the service, and things (generally :-) ) work.

Anyways, that's what I'm thinking. Let me know if you have questions or suggestions, especially about the last two bullet points.

Thanks,
Mark
(Here I'm using the @ sign after a word to designate a group name. Annoying? Useful? Meh?)


locked Re: Early 2016 Roadmap

Steph <hsrsp@...>
 

How about keeping this one as beta@ and have a sub group called GroupManagers@

Sent: Monday, January 04, 2016 12:34 PM
Subject: [beta] Early 2016 Roadmap

Hi all,

I hope you all had a good New Year! While I did monitor beta@ during my vacation, it will take me a few days to go through and respond to the various threads from the past couple weeks. I appreciate your patience.

I've been thinking about what I'd like to get accomplished in the first part of this year. Here are my thoughts. Groups.io has been in quasi-beta status since launch (quasi because I haven't really made a big deal about it). I'd like to officially move out of beta status. To get there, I'd like to complete the following:

- Complete the database feature.
- Complete the long in-progress subdomains feature.
- Figure out what the Enterprise plan will be, if there is one.
- Work on some of the issues discussed over the past two weeks, including invite and join flows, and permissions.
- Bugfixes, of course.
- Decide whether beta@ should be renamed, and if so, to what.
- Figure out if there's anything I can or should be doing to funnel people to GroupManagersForum@ and similar groups, both to reduce traffic on beta@ and to keep its' scope more focused on development/improvement of the service.

Moving out of beta status will not have any real effect on the service. I will continue development in the same manner as now. Like all software development, there will still be bugs. It's more to say that we've been around over a year now, lots of people use the service, and things (generally :-) ) work.

Anyways, that's what I'm thinking. Let me know if you have questions or suggestions, especially about the last two bullet points.

Thanks,
Mark
(Here I'm using the @ sign after a word to designate a group name. Annoying? Useful? Meh?)


locked Re: Early 2016 Roadmap

 

Agreed. I like the idea of officially coming out of beta. This way I can tell my group we're not moving to something that's not still 'in the testing phase' (whatever that means;).

One question: will the pricing structure change with this now, or will that be later? We're getting an ad-free experience now, which will be pleasant for group members (and a pleasant change from yahoo). When can we expect that to change on them? This may affect decisions (mine and other group owners') about if and when to upgrade. Thanks!
J

Sent from my iPhone

On Jan 4, 2016, at 10:43 AM, Christopher Hallsworth <challsworth2@icloud.com> wrote:

Nothing of the sort here, but what an awesome service it has been for me personally! It broke down a few times, but what do you expect? This is what I expect from this and any other service, whose experienced has been mixed for me, Emissives/Mailman being the worst possible both in terms of stability and support. Keep it up, and it would be awesome if it could come out of beta status in the not too distant future. It certainly didn't feel like a beta to me, and still doesn't. I think you should rename this group "development" or something of the sort. Looking forward to using Groups.io in 2016 and subsequent years.
On 4 Jan 2016, at 18:34, Mark Fletcher <markf@corp.groups.io> wrote:

Hi all,

I hope you all had a good New Year! While I did monitor beta@ during my vacation, it will take me a few days to go through and respond to the various threads from the past couple weeks. I appreciate your patience.

I've been thinking about what I'd like to get accomplished in the first part of this year. Here are my thoughts. Groups.io has been in quasi-beta status since launch (quasi because I haven't really made a big deal about it). I'd like to officially move out of beta status. To get there, I'd like to complete the following:

- Complete the database feature.
- Complete the long in-progress subdomains feature.
- Figure out what the Enterprise plan will be, if there is one.
- Work on some of the issues discussed over the past two weeks, including invite and join flows, and permissions.
- Bugfixes, of course.
- Decide whether beta@ should be renamed, and if so, to what.
- Figure out if there's anything I can or should be doing to funnel people to GroupManagersForum@ and similar groups, both to reduce traffic on beta@ and to keep its' scope more focused on development/improvement of the service.

Moving out of beta status will not have any real effect on the service. I will continue development in the same manner as now. Like all software development, there will still be bugs. It's more to say that we've been around over a year now, lots of people use the service, and things (generally :-) ) work.

Anyways, that's what I'm thinking. Let me know if you have questions or suggestions, especially about the last two bullet points.

Thanks,
Mark
(Here I'm using the @ sign after a word to designate a group name. Annoying? Useful? Meh?)



locked Re: Early 2016 Roadmap

christopher hallsworth <challsworth2@...>
 

Nothing of the sort here, but what an awesome service it has been for me personally! It broke down a few times, but what do you expect? This is what I expect from this and any other service, whose experienced has been mixed for me, Emissives/Mailman being the worst possible both in terms of stability and support. Keep it up, and it would be awesome if it could come out of beta status in the not too distant future. It certainly didn't feel like a beta to me, and still doesn't. I think you should rename this group "development" or something of the sort. Looking forward to using Groups.io in 2016 and subsequent years.

On 4 Jan 2016, at 18:34, Mark Fletcher <markf@corp.groups.io> wrote:

Hi all,

I hope you all had a good New Year! While I did monitor beta@ during my vacation, it will take me a few days to go through and respond to the various threads from the past couple weeks. I appreciate your patience.

I've been thinking about what I'd like to get accomplished in the first part of this year. Here are my thoughts. Groups.io has been in quasi-beta status since launch (quasi because I haven't really made a big deal about it). I'd like to officially move out of beta status. To get there, I'd like to complete the following:

- Complete the database feature.
- Complete the long in-progress subdomains feature.
- Figure out what the Enterprise plan will be, if there is one.
- Work on some of the issues discussed over the past two weeks, including invite and join flows, and permissions.
- Bugfixes, of course.
- Decide whether beta@ should be renamed, and if so, to what.
- Figure out if there's anything I can or should be doing to funnel people to GroupManagersForum@ and similar groups, both to reduce traffic on beta@ and to keep its' scope more focused on development/improvement of the service.

Moving out of beta status will not have any real effect on the service. I will continue development in the same manner as now. Like all software development, there will still be bugs. It's more to say that we've been around over a year now, lots of people use the service, and things (generally :-) ) work.

Anyways, that's what I'm thinking. Let me know if you have questions or suggestions, especially about the last two bullet points.

Thanks,
Mark
(Here I'm using the @ sign after a word to designate a group name. Annoying? Useful? Meh?)


locked Early 2016 Roadmap

 

Hi all,

I hope you all had a good New Year! While I did monitor beta@ during my vacation, it will take me a few days to go through and respond to the various threads from the past couple weeks. I appreciate your patience.

I've been thinking about what I'd like to get accomplished in the first part of this year. Here are my thoughts. Groups.io has been in quasi-beta status since launch (quasi because I haven't really made a big deal about it). I'd like to officially move out of beta status. To get there, I'd like to complete the following:

- Complete the database feature.
- Complete the long in-progress subdomains feature.
- Figure out what the Enterprise plan will be, if there is one.
- Work on some of the issues discussed over the past two weeks, including invite and join flows, and permissions.
- Bugfixes, of course.
- Decide whether beta@ should be renamed, and if so, to what.
- Figure out if there's anything I can or should be doing to funnel people to GroupManagersForum@ and similar groups, both to reduce traffic on beta@ and to keep its' scope more focused on development/improvement of the service.

Moving out of beta status will not have any real effect on the service. I will continue development in the same manner as now. Like all software development, there will still be bugs. It's more to say that we've been around over a year now, lots of people use the service, and things (generally :-) ) work.

Anyways, that's what I'm thinking. Let me know if you have questions or suggestions, especially about the last two bullet points.

Thanks,
Mark
(Here I'm using the @ sign after a word to designate a group name. Annoying? Useful? Meh?)


locked Re: Calendar #bug

Ella Yu <ellaxyu@...>
 

I totally agree. This isn't an exact bug.

----- Original Message -----
From: "Shal Farley" <shals2nd@gmail.com
To: beta@groups.io
Date sent: Sun, 03 Jan 2016 13:02:38 -0800
Subject: Re: [beta] Calendar #bug

Duane,

I have my groups set so that "Subscribers can view and edit" the
calendar. I added an event some time ago and another member was going
to update it this morning, but didn't have editing capability. I tried
with my member account and ran into the same thing.

I wouldn't consider this a bug. Like deleting/editing messages and other content, if you're not a moderator you should be able to make changes only to your own content.

In other words, I don't think members ought to be allowed to edit each other's events - I'd consider that the bug if they could.

-- Shal


locked Re: Calendar #bug

Janice B <weebee.1@...>
 

It is my understanding that if you have only moderator able to edit, that an individual cannot edit any files for photos unless they are a moderator. It doesn't matter if they uploaded it or not. This is real problematic for my group. I hope Mark will come up with an option where they can edit anything they have uploaded if they are an ordinary member.

Janice B
AZ
Remember...stressed is desserts spelled backwards

On Jan 3, 2016, at 2:02 PM, Shal Farley <shals2nd@gmail.com> wrote:

Duane,

I have my groups set so that "Subscribers can view and edit" the
calendar. I added an event some time ago and another member was going
to update it this morning, but didn't have editing capability. I tried
with my member account and ran into the same thing.
I wouldn't consider this a bug. Like deleting/editing messages and other content, if you're not a moderator you should be able to make changes only to your own content.

In other words, I don't think members ought to be allowed to edit each other's events - I'd consider that the bug if they could.

-- Shal




locked Re: Calendar #bug

Duane
 

Shal,

I hadn't really looked at it like that. If that's the consensus, then I'd like to be able to specify who can edit an event, either individual names or group wide. Our groups tend to have an open approach to events. One person will post it, another will add a few details, then possibly another add or correct previous information. I'd rather see events moderated before changes go live than prevent the assistance of others completely. So many ways to look at things!

Duane


locked Re: Calendar #bug

 

Duane,

I have my groups set so that "Subscribers can view and edit" the
calendar. I added an event some time ago and another member was going
to update it this morning, but didn't have editing capability. I tried
with my member account and ran into the same thing.
I wouldn't consider this a bug. Like deleting/editing messages and other content, if you're not a moderator you should be able to make changes only to your own content.

In other words, I don't think members ought to be allowed to edit each other's events - I'd consider that the bug if they could.

-- Shal


locked Calendar #bug

Duane
 

I have my groups set so that "Subscribers can view and edit" the calendar. I added an event some time ago and another member was going to update it this morning, but didn't have editing capability. I tried with my member account and ran into the same thing.

I probably should send this to the support address, but thought others might want to check and/or be aware of it.

Duane


locked "advanced subscription options"

 

I don't know whether the "advanced" subscription options are new or I just never noticed them before, but just want to say that this is an awesome feature.

J_Olivia


locked polls #suggestion

Duane
 

Having used the poll feature a couple of times, I've realized there are a couple of things that I'd like to see added or changed. The first would be to have a Close Date for when the poll would end and the thread be closed automatically. Choices of one week and one month seem most likely, but I'm sure others might have different preferences. I know we can do this with the hashtag, but only one Duration can be used for each.

The second would be an option to make the thread sticky. I find I'm doing that anyway, so having the option on the creation page would be nice. This might reduce the need for a closing date, especially for those like me that do things online. We'd be more apt to see the thread on a regular basis and remind ourselves to close it.

Thanks,
Duane


locked Re: how to reach all members of a group

 

I make it a policy of my groups up front that "No Mail" is not an option;  if you want to join my groups you have to select "Special Notices" at a minimum.

Every so often I go through my groups and bulk change the people who switched to "No Mail" back to "Special Notices".  The way I see it, if you want to join my groups then you have to accept "Special Notices" at the minimum so that the rest of the members don't have to deal with the inevitable posts asking about the tings that the "No Mail" members failed to get word of.  Those people who don't want to at least accept the occasional "Special Notice" are free to unsubscribe or not join at all.  I don't charge anything to be a member of my groups, so to those people who don't like it I tell them that receiving an occasional "Special Notice" is a small price to pay.  I've had this policy for over eight years now and for the most part it's a non-issue when it's made clear up front that that's a rule (and the price one pays) for joining the group.

Mark Bielecki


locked Re: how to reach all members of a group

Janice B <weebee.1@...>
 

Actually, you can click on Delivery again and it reverses the order so your No Mail members come up first. This re-ordering is temporary and when you leave the members tab, the next time you visit it the list will be in the standard order. NOTE|. By clicking on the other headings you can get other sortings of the members list like Date.

Janice B
AZ
Remember...stressed is desserts spelled backwards

On Jan 2, 2016, at 1:22 PM, David P. Dillard <jwne@temple.edu> wrote:



"> I just did it for my 725 member group. Look at the members list and if
you click on Delivery it reorders the list grouping everyone according
to the Delivery method they have chosen. My No Mail members were
gathered at the end of the list and there were only 10 set to No Mail."

It just goes to figure, this is Groups.IO. There is going to be a sensible and intelligent way to do just about anything you need and if there is not, it gets reported with a good chance an intelligent solution will be on the way soon thereafter. <g>



Sincerely,
David Dillard
Temple University
(215) 204 - 4584
jwne@temple.edu


On Sat, 2 Jan 2016, weebeequilting wrote:

I just did it for my 725 member group. Look at the members list and if you click on Delivery it reorders the list grouping everyone according to the Delivery method they have chosen. My No Mail members were gathered at the end of the list and there were only 10 set to No Mail. I could easily copy those down and send them an email message from my personal email address. This is not something I would do on any kind of a regular basis, but it gives me the option to reach EVERYONE if I absolutely need to.

Janice B
AZ
Remember...stressed is desserts spelled backwards


On Jan 2, 2016, at 7:15 AM, Carlos <carlos1106@nyc.rr.com> wrote:

But again once the number of group members starts to add up, even determining which members are configured for "no mail" is not practical.

----- Original Message ----- From: "weebeequilting" <weebee.1@cox.net>
To: <beta@groups.io>
Sent: Saturday, January 02, 2016 9:10 AM
Subject: Re: [beta] how to reach all members of a group


When I want to reach just about everyone, I send my message as a Special Notice. It will go out to everyone except those who are set at no mail. If the number of no mail members is low, you could copy their email addresses and send a message to them from a non Groups.io email address.

Just a thought.

Janice B
AZ
Remember...stressed is desserts spelled backwards


On Jan 2, 2016, at 7:02 AM, Carlos <carlos1106@nyc.rr.com> wrote:

LOL not very practical if you have even 50 or so members, never mind hundreds.
----- Original Message ----- From: "Rajmund" <brajmund2000@gmail.com>
To: <beta@groups.io>
Sent: Saturday, January 02, 2016 8:19 AM
Subject: Re: [beta] how to reach all members of a group


Hello,
Just an idea. Get all their email. Put them in the BCC, put yourself into the to field, and send them an email.

----- Original Message -----
From: Adrien Collins <adriencollins22160@gmail.com>
To: beta@groups.io
Date: Saturday, January 2, 2016 12:58 pm
Subject: [beta] how to reach all members of a group



Hi


How can I reach all members of my group, even those who are
on no mail?
Regards

Adrien


-----Original Message-----
From: kr402 via Groups.io [mailto:kr402=yahoo.com@groups.io]

Sent: Saturday, January 02, 2016 6:40 AM
To: beta@groups.io
Subject: Re: [beta] URL with comma in plain text mode

On Jan 1, 2016, at 10:29 PM, "JohnF via Groups.io"
<johnf1686=yahoo.com@groups.io> wrote:

Thanks for checking this from other sources.
you are welcome.

It looks like it is probably just Yahoo screwing up.
Nothing too unusual about that.
no unfortunately it is not, but then that is why we are at
groups.io instead of Ygrouos.

KR
Sent from a Braille Sense