book / act Goto Github PK

There are many 23 bit public key IDs that have collisions already, see http://evil32.com

The key ID field should fit the full fingerprint or 64 bit IDs at least.

There should be an email out each week to all unconfirmed talks until the speakers confirm or cancel.

The Wiki toolkit needs updated because it is very easily broken, and lacks lots of features that would be nice to have.

There are many cases when the person who attends the event
and the person who actually makes the payment are different.

It would be nice if this could be supported by Act as well.

Maybe it is enough to allow payment for one person without being logged in.
That way the person who attends can register and the paying person can just select one or more (!) attendees and pay.

The receipt that is auto-generated out of ACT is not acceptable. There needs to be a template that can be edited to allow for a proper email receipt.

Currently the schedule view is all or nothing.

It'd be nice to have a schedule view for just a particular room. This would especially be useful for printing out room schedules to be put outside of rooms at the conferences.

Suggested by Rolf Langsdorf (YAPC::EU 2012)
Currently, only one speaker can be assigned a given talk, even though some talks are actually done by more than one speaker.

Hey @book, could you merge the PSGI branch by chance?

Talks should have 'real' descriptions and 'teaser' descriptions.

The YAPC admins can see real descriptions but the teasers are shown until the talk is finished and then ACT shows the real description (and maybe a link to see the teaser as well afterward)

Have an RSS feed of "Accepted Talks" to make pushing news easier.

Each ACT owner likes to create their own layout/CSS, but maybe we should have a standard print CSS that works regardless, and they can edit it if they want? This would allow printing of good schedules.

Suggested by Rolf Langsdorf (YAPC::EU 2012)
It is necessary to ask speakers their permission to record them on video and make the video public. The task could be simplified by adding a checkbox on the talk form, so the organisers already know the speaker who agree on that.

Currently, the user information is mostly in the "user", with a few bits in the "participations" table (like the tshirt size). Adding new fields means updating the database schema, and applies to all conferences.

There is therefore a need for a generic key/value system, which should ideally be configurable by the conference organizers, from act.ini as a good start, through a web interface.

Lighting Talk Speakers are not Conference speakers and should be dealt with differently. There needs to be a way to not allow Lighting Talk speakers to get a free registration. They should be created as a separate class.

For figuring out which talks are the most interesting, members of talks_admin can add unapproved talks to their schedule.
Clicking on the star results in the name being added to the list, but after that you can click again, even if you reload the page. Then the name is added multiple times to the list. Also the count increases on the favorite talks page.

And there is no way to remove the talk from your schedule again.

Show the Twitter account on the user profile page:

• either by using the PAUSE ID to retrieve the information from MetaCPAN
• or from a Twitter field in Act (not all users have a CPAN account). See issue #29.

Use the Twitter "follow" button.

ACT uses Jquery from 2009. It doesn't even work with older Jquery projects, like
http://www.basic-slider.com/.

Can we please upgrade this?

Regards
Racke

life od ### life****

Because the session ID currently is stored in the "users" table, one can not be logged on more than one conference on an Act instance. Although not a big issue, it is very annoying when one attends to several conferences and has to sign out and sign in each time.

13:19 [Nicholas] http://act.yapc.eu/ye2012/stats -- There are 5 registered people coming from 4 countries and 5 monger groups. There are committed users, that is to say, people that either paid their conference ticket or will give a talk.
13:19 [Nicholas] there are committed users. Not 0, zero, or no

The ACT html is hopelessly old and broken. There are

The html should be revised to be semantic, using tables only for tabular data. This will make it much easier for conference organizers to style their sites.

While setting up i ended up using an empty ACTHOME directory, which meant that i got all sorts of weird errors because certain handlers couldn't find their files (template, I18N) and failed silently.

Act should help the participants to communicate between themselves.

It would be helpful to display on a single page a list of users who have at least on messaging account on their profile:

• IRC
• IM
• Twitter (see issue #30)

To protect against generic crawlers, access this list could be limited to logged in users.

There are many wiki pages that could have generated content from a template when an ACT instance is set up, this support should be added.

The changepwd form can be confusing by showing the "current password" field even when invoked via the lost password procedure. In this precise case, it should be hidden.

Suggested by Rolf Langsdorf (YAPC::EU 2012)
Currently, a talk title only appears in the page title, confusing users. Modify the default template so the talk title appears in the content of the page.

A continuation of the discussion started in metacpan issues the subject being the non consent of attendee's data sharing between services.

This file is a compilation of publicly available data.
When we create an account in Act, it is not said that the data may be compiled and made publicly available outside of the conference.

How will be handled the requests to be removed from this compilation, without being removed from the conferences ?

I'm in favor of a consent checkbox, active opt-in.

• Publicly available for this conf only
• Publicly available for all conferences
• Publicly available for all conf and ok for sharing data

All unchecked by default.

Btw we could ask ourself the relevance of keeping publicly available information about visitors after a conference.

Witness: http://act.perl-workshop.ch/spw2017/user/11869 - the link to the Alpine Perl Workshop 2016 is missing / between the conference name and user/ so results in a 404. Compare: http://act.perl-workshop.ch/spw2017/user/10652 - only the Alpine Perl Workshop 2016 is affected here so must be an issue with the URL as entered for that conference.

Fix needs to happen in https://github.com/book/Act/blob/master/templates/core/user/show#L199

I would look at this but need to build myself an Act VM to work with - do you have anything to automate that or is this a case of "well volunteered"?

starring and unstarring the second of two back-to-back sessions of http://www.yapcna.org/yn2013/talk/4734 modifies the starred count for the first session of the talk by appending a new string value to the star count, rather than replacing the numeric starred value . it does not affect the starred count for the second session of the talk at all.

e.g. the count for the first session ('43') becomes '4344' after the first star/unstar, while the count for the second session remains '43'. after a second star/unstar, the first session count becomes '434443', and the second session count remains '43'.

Getting ACT into Github was a wonderful first step to opening up hacking. Getting ACT running on PSGI/Plack will be an excellent second setup. It will mean people don't have to set up mod_perl for doing development, something which even back in the day wasn't exact a trivial first step.

Currently, when you create events they must be attached to a 'Room'. This is not ideal, as things like 'break', 'lunch', 'breakfast', etc may not be tied to any particular room.

We should allow for events to be created that are not attached to particular rooms but still show up on the schedule somewhere, without pushing other items in the schedule around.

There needs to be a new role for sponsors. Where they can log in and bulk register who is going to attend. The bulk registration should be or <first, last, email> where the later would auto generate a junk password.

Add a field in the profile for Twitter username.

ACT needs to be able to do bulk emailing off of a template.

For example: Bulk email registered but unpaid people. It was asked to consider adding bulk actions to the users page for mass accept or mass email.

curl http://localhost:5000/yapcna/css/act-base.css # returns the login page.

Just wanted to get this recorded in a central place; I'm going to look into this tonight.

Facebook Connect for ACT (This may already be possible)

Right now a lot of important information about each conference is stored in a config file that can only be edited from a shell on the hosting machine. All (or maybe just most) of this information should be exposed to conference admins via the web.

The current HTML title of a news entry is only "News".

The distinction that ACT makes between registration and purchasing a ticket is extremely confusing. The distinction is meaningless for most attendees, and leads to people not realizing that they haven't actually registered.

I think for the short term, ACT should be changed so that account creation simply goes straight to the ticket purchasing page. Longer term, I think the internals should be changed to eliminate this distinction entirely.

The question is how to handle free conferences like LPW. This should probably be special cased with some sort of "free conference" flag in the configuration, so that instead of going to the payment page people are taken to a "confirm you will actually attend" page.

One of the main consequences of this change is that the pages which list attendees should only show confirmed attendees (people who've paid) rather than what they currently show.

During scheduling session for OSDC.fr 2012, two rooms where no talk was scheduled yet were not displayed, hence confusing...

So, when a room is added, get it on the schedule, even if no talk is scheduled yet in it.

ACT needs to have a badge template that can be edited and the conference administrators can generate a PDF for print directly out of ACT.

The goal is to rely on OpenID Connect to be able to delegate authentication to OpenID Connect Providers like Google, Facebook, Twitter, etc.

OpenID Connect: http://openid.net/connect/

Currently events do not show up on personal schedules. They should.

Hi,

many messages in the PO files are cut-off after some number of characters.
See e.g.
"This operation requires a confirmation. Please enter your email address,"
"An email has been sent to . Click on the link in the email to"
"The personal data that will be gathered here will be used to create"

and so on.

as per http://blogs.perl.org/users/shlomi_fish/2012/10/please-publish-perl-events-on-the-lwnnet-calendar.html

it would be awesome if act could notify a range of sites and online calendars of upcoming events. at the most basic level send them an email from a template, or perhaps use an API or WWW::Mechanise to fill out a form.

on the above post, a number of sites are listed.

Currently, BOFs are events, but it would be better if they were treated like talks, where users could submit BOF requests for open time slots directly.