simone960's picture

I wonder where I can make a request to have a particular module to be ported properly and made available to the community as not all of us are developers. Some modules are pretty helpful and not yet ported. Perhaps a place where people can make suggestion and able to vote other suggested modules and eventually backdrop's developers can take serious consideration to port them to backdrop and make it publicly available would be great.

Accepted answer

Hello @simone960

You can make a port request here: https://github.com/backdrop-ops/contrib/issues

tag it with `Port Request`.

Most helpful answers

...one possibility is to have a Drupal -> Backdrop module port thread here on the forum. At the time of the original port request on GitHub we did not have a forum.

I like this idea! Actually the community can first make a request and take a vote here in this forum. Backdrop team will then review and evaluate the request and those modules that are worth considering, potential and likely to be ported can then be moved over to the GitHub for further discussion and implementation. This will help to filter out too many requests on GitHub to be attended which some are unlikely to be considered for porting.

GitHub to me personally is more like a working and a gathering place for developers instead of ordinary users. Besides, the current forum is very well designed, it looks beautiful, pleasant, attractive and welcoming (Good job! designer! ). Since we have the forum now, why not make a good use of it just to bring people together and build up the community here instead of elsewhere. 

Having said that, I'm not sure if it is better to open another new category on its own for this purpose. If we only have everything posted within a single post, it's going to be a long post and may not be easy for review when getting more and more requests and comments. Perhaps one request per post is better in long term, this will get things focused and people can share further the reason why they support such module to be ported. I think the considering factors to have a module ported should not only be limited to only it's popularity and votes but also other factors like necessity, or for some, key factor for migration over to backdrop. That's my little thoughts.

Others ?

 

P/s: OSTraining has a Vote on New Classes worth checking out for some ideas. 

@simone960 I see your point about GitHub.

I find GitHub easy to use, but I'll admit not necessarily everyone interested in Backdrop is interested in or has a GitHub account. I'm not sure what the best solution is, but one possibility is to have a Drupal -> Backdrop module port thread here on the forum. At the time of the original port request on GitHub we did not have a forum.

Part of the reason for the forum is to find some middle ground communicating with people interested in Backdrop so maybe this is the best place for the port request thread.

Thoughts?

Comments

I wonder the same thing. There sould be at least a page with comments open so people can suggest modules names and maybe vote (give a +1) to suggestions.

simone960's picture

Thanks @serundeputy for the link and instruction ! Though not everyone would be comfortable to use github but at least there's a place to make such request at the moment. Thanks!

@simone960 I see your point about GitHub.

I find GitHub easy to use, but I'll admit not necessarily everyone interested in Backdrop is interested in or has a GitHub account. I'm not sure what the best solution is, but one possibility is to have a Drupal -> Backdrop module port thread here on the forum. At the time of the original port request on GitHub we did not have a forum.

Part of the reason for the forum is to find some middle ground communicating with people interested in Backdrop so maybe this is the best place for the port request thread.

Thoughts?

simone960's picture

...one possibility is to have a Drupal -> Backdrop module port thread here on the forum. At the time of the original port request on GitHub we did not have a forum.

I like this idea! Actually the community can first make a request and take a vote here in this forum. Backdrop team will then review and evaluate the request and those modules that are worth considering, potential and likely to be ported can then be moved over to the GitHub for further discussion and implementation. This will help to filter out too many requests on GitHub to be attended which some are unlikely to be considered for porting.

GitHub to me personally is more like a working and a gathering place for developers instead of ordinary users. Besides, the current forum is very well designed, it looks beautiful, pleasant, attractive and welcoming (Good job! designer! ). Since we have the forum now, why not make a good use of it just to bring people together and build up the community here instead of elsewhere. 

Having said that, I'm not sure if it is better to open another new category on its own for this purpose. If we only have everything posted within a single post, it's going to be a long post and may not be easy for review when getting more and more requests and comments. Perhaps one request per post is better in long term, this will get things focused and people can share further the reason why they support such module to be ported. I think the considering factors to have a module ported should not only be limited to only it's popularity and votes but also other factors like necessity, or for some, key factor for migration over to backdrop. That's my little thoughts.

Others ?

 

P/s: OSTraining has a Vote on New Classes worth checking out for some ideas. 

I just created a port request on github, but am unable to "tag" the issue myself. Apparently, I don't have clearance for that. 

I think that without a voting tool this topic will become an unmanageable mess pretty soon.

It's a possibility to have a first comment establishing request rules like

  • do not discuss the validity of requests here
  • post the correct full module name
  • and one request per post only

and a second one gathering all different requests in a single list.

It will be possible to count the number of requests for any particular module with a simple Ctrl+F.

But this will have to be done for every single module name and someone will have to donate a lot of time to manage this main list.

It is easier and possibly cheaper to create an external site specifically for that in a shared host.

Cheers.

Has there been any more thought given to some kind of module request / interest page either on the main site or on this one? I feel like I've seen some comments elsewhere but I'm not finding them.

Many times I've found that some Drupal 7 module I used all the time has no port or port request. I wonder how many other people went looking for a particular module and, not finding it, just walked away. For example, I know of 3 separate sites I still do work for that are still on D7, and in many ways fit the profile of a Backdrop user: small site, small/no staff, too complex / interactive for WordPress. But they require several modules with no or incomplete ports: Organic Groups, Rules, Realname, etc. Is it really the case that no other current or potential Backdrop users are building these kinds of sites?

I don't know, maybe people aren't any more likely to vote for a module in a list than to comment in a forum, or add a request issue on Github. It seems like it would be nice to make it as easy as possible, but the infrastructure effort required isn't nothing.